Skip to content
GitLab
Explore
Sign in
Primary navigation
Search or go to…
Project
Y
YAC
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
Container Registry
Model registry
Operate
Environments
Monitor
Incidents
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
dkrz-sw
YAC
Commits
457f24cb
Commit
457f24cb
authored
5 months ago
by
Moritz Hanke
Browse files
Options
Downloads
Patches
Plain Diff
adds workaround for Intel ICX bug
parent
db559d0d
No related branches found
Branches containing commit
No related tags found
Tags containing commit
No related merge requests found
Changes
1
Hide whitespace changes
Inline
Side-by-side
Showing
1 changed file
tests/common/test_common.c
+9
-0
9 additions, 0 deletions
tests/common/test_common.c
with
9 additions
and
0 deletions
tests/common/test_common.c
+
9
−
0
View file @
457f24cb
...
...
@@ -62,7 +62,16 @@ int intersect(enum yac_edge_type edge_type_a,
double
lon_c
,
double
lat_c
,
double
lon_d
,
double
lat_d
,
double
*
intersection
)
{
// Intel ICX with O3 seems to use some vector operation for copying q to
// intersection in the code below. However, this causes a segmentation vault
// due to the alignment of q. By increasing the size of p to 4, the alignment
// of q is correct.
#define INTEL_ICX_BUG
#ifdef INTEL_ICX_BUG
double
a
[
3
],
b
[
3
],
c
[
3
],
d
[
3
],
p
[
4
],
q
[
3
];
#else
double
a
[
3
],
b
[
3
],
c
[
3
],
d
[
3
],
p
[
3
],
q
[
3
];
#endif
LLtoXYZ_deg
(
lon_a
,
lat_a
,
a
);
LLtoXYZ_deg
(
lon_b
,
lat_b
,
b
);
...
...
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