- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Correction to my previous comment on this subject. I had been using a hidden setting of -standard-semantics for recent versions of ifort. Now with 16.0.1 the combination of options -standard-semantics -Qxhost -Qopt-report produces internal compiler error while processing maxloc. If I remove opt-report it runs, but optimization of maxloc is disabled. Setting -assume:old_maxminloc fixes the ICE and restores optimization. I assume this makes the 0-length operand case non-conformant with f2003 but didn't test that. Setting -arch:SSE4.1 also avoids the ICE.
Link Copied
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
C'mon, Tim, you know the drill. Please provide a source so that we can investigate.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Need lcd_mod.mod or the source file to generate the module file.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Thanks - I can reproduce this and will escalate to development. Issue ID is DPD200379011.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
The developers tell me that this is a bug they recently fixed and that the fix will appear in Update 2.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Good to see that it will be fixed. It has been difficult to understand why complying with f2003 causes so much trouble.
ifort may be unrolling the inner loop excessively. It doesn't perform as well as Intel C, which has only a single AVX2 parallel comparison in the inner loop of function s3110 (where the ifort bug appears to be). That's only a nit pick, as ifort performs much better on this case than any non-Intel compiler I've been able to test.
The unrolling in this case doesn't appear to be affected by /Qunroll or unroll directive.
VTune doesn't seem to show excessive remainder loop time.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
It's not "complying with F2003", but the 2003-compatible operations exposed a bug in the optimizer.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
16.0.2 seems to support full optimization without old_maxminloc.
- Subscribe to RSS Feed
- Mark Topic as New
- Mark Topic as Read
- Float this Topic for Current User
- Bookmark
- Subscribe
- Printer Friendly Page