[Bug c/70255] New: change of the order of summation of floating point numbers despite no-associative-math

2016-03-18 Thread shatz at dsit dot co.il
Severity: normal Priority: P3 Component: c Assignee: unassigned at gcc dot gnu.org Reporter: shatz at dsit dot co.il Target Milestone: --- Created attachment 37989 --> https://gcc.gnu.org/bugzilla/attachment.cgi?id=37989&action=edit minimal test

[Bug c/70255] change of the order of summation of floating point numbers despite no-associative-math

2016-03-19 Thread shatz at dsit dot co.il
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=70255 --- Comment #8 from shatz at dsit dot co.il --- Now a bit of philosophy. Bugs aside, I should say that use of function attribute optimize() does not look to me as an ideal solution for forcing ISO rules. >From theoretical point of view, when

[Bug c/70255] change of the order of summation of floating point numbers despite no-associative-math

2016-03-19 Thread shatz at dsit dot co.il
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=70255 --- Comment #7 from shatz at dsit dot co.il --- (In reply to Richard Biener from comment #1) > Confirmed. The issue seems to be that you add the optimize attribute after > the function definition. > > This causes .original t

[Bug c/70255] change of the order of summation of floating point numbers despite no-associative-math

2016-05-10 Thread shatz at dsit dot co.il
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=70255 --- Comment #12 from shatz at dsit dot co.il --- (In reply to Marek Polacek from comment #11) > I added the warning, so closing as fixed. Warning is nice, but IMHO it is far more important to document the behavior in online documentat

[Bug c/70255] change of the order of summation of floating point numbers despite no-associative-math

2016-05-10 Thread shatz at dsit dot co.il
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=70255 --- Comment #14 from shatz at dsit dot co.il --- (In reply to Marek Polacek from comment #13) > So what exactly is not documented? > > And I disagree that a warning isn't necessary just because something is > documented --

[Bug c/70255] change of the order of summation of floating point numbers despite no-associative-math

2016-05-11 Thread shatz at dsit dot co.il
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=70255 --- Comment #18 from shatz at dsit dot co.il --- (In reply to Manuel López-Ibáñez from comment #15) > (In reply to shatz from comment #14) > > It is not documented that __attribute__((optimize(""))) works reliably when >

[Bug c/70255] change of the order of summation of floating point numbers despite no-associative-math

2016-05-19 Thread shatz at dsit dot co.il
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=70255 --- Comment #20 from shatz at dsit dot co.il --- (In reply to Marek Polacek from comment #19) > Markus recently committed a patch (r235580) that points out that this > attribute should only be used for debugging. 3 weeks after the patch I

[Bug c/70255] change of the order of summation of floating point numbers despite no-associative-math

2016-05-19 Thread shatz at dsit dot co.il
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=70255 --- Comment #22 from shatz at dsit dot co.il --- (In reply to Jakub Jelinek from comment #21) > It can't be changed in those manuals, ever, both 6.1 and 5.3 releases have > already been released, their documentation, including onli

[Bug middle-end/80283] [5/6/7/8 Regression] bad SIMD register allocation

2017-08-08 Thread shatz at dsit dot co.il
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=80283 shatz at dsit dot co.il changed: What|Removed |Added CC||shatz at dsit dot co.il