Skip to content
GitLab
Explore
Sign in
Primary navigation
Search or go to…
Project
D
dune-uggrid
Manage
Activity
Members
Labels
Plan
Issues
Issue boards
Milestones
Wiki
Code
Merge requests
Repository
Branches
Commits
Tags
Repository graph
Compare revisions
Build
Pipelines
Jobs
Pipeline schedules
Artifacts
Deploy
Releases
Model registry
Operate
Environments
Monitor
Incidents
Service Desk
Analyze
Value stream analytics
Contributor analytics
CI/CD analytics
Repository analytics
Model experiments
Help
Help
Support
GitLab documentation
Compare GitLab plans
Community forum
Contribute to GitLab
Provide feedback
Keyboard shortcuts
?
Snippets
Groups
Projects
Show more breadcrumbs
staging
dune-uggrid
Commits
f3a01f79
Commit
f3a01f79
authored
11 years ago
by
Oliver Sander
Browse files
Options
Downloads
Patches
Plain Diff
Fix English language errors
parent
8da3b4a1
No related branches found
No related tags found
No related merge requests found
Changes
2
Hide whitespace changes
Inline
Side-by-side
Showing
2 changed files
parallel/ddd/mgr/objmgr.c
+1
-1
1 addition, 1 deletion
parallel/ddd/mgr/objmgr.c
parallel/dddif/handler.c
+1
-1
1 addition, 1 deletion
parallel/dddif/handler.c
with
2 additions
and
2 deletions
parallel/ddd/mgr/objmgr.c
+
1
−
1
View file @
f3a01f79
...
...
@@ -566,7 +566,7 @@ DDD_IndexObject::DDD_IndexObject (DDD_TYPE typ,
Remove object's header from DDD management.
This function removes an object from DDD-management
via destructing its \ddd{header}.
{\em Note:} The \ddd{object} will be destr
uct
ed, but its copies
{\em Note:} The \ddd{object} will be destr
oy
ed, but its copies
on remote processors will not be informed by \funk{HdrDestructor}.
There are two consistent possibilities to delete \ddd{objects} which
have copies on remote processors:
...
...
This diff is collapsed.
Click to expand it.
parallel/dddif/handler.c
+
1
−
1
View file @
f3a01f79
...
...
@@ -615,7 +615,7 @@ static void VectorObjMkCons (DDD_OBJ obj, int newness)
NOTE (TODO): this might be too less. for n2n transfer, connections
might be set up consisting of two matrix structures transfered from
different procs. this code will NOT handle that case, the connection
will be created with the first matrix and destr
uct
ed here.
w
hen the
will be created with the first matrix and destr
oy
ed here.
W
hen the
second message arrives, the second matrix will lead to construction
of a second connection, which will also be deleted here. we would
need a mkcons after all messages to handle that case. (NIY in ddd 1.6.5)
...
...
This diff is collapsed.
Click to expand it.
Preview
0%
Loading
Try again
or
attach a new file
.
Cancel
You are about to add
0
people
to the discussion. Proceed with caution.
Finish editing this message first!
Save comment
Cancel
Please
register
or
sign in
to comment