https://gcc.gnu.org/bugzilla/show_bug.cgi?id=91974
--- Comment #11 from Jakub Jelinek ---
Author: jakub
Date: Thu Nov 21 17:12:57 2019
New Revision: 278577
URL: https://gcc.gnu.org/viewcvs?rev=278577&root=gcc&view=rev
Log:
Backported from mainline
2019-10-04 Jakub Jelinek
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=91974
--- Comment #10 from Jakub Jelinek ---
The originally reported issue fixed for 9.3+ too. Not really sure if it is a
good idea to backport the shift and array ref changes, those are quite
invasive.
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=91974
--- Comment #9 from Jakub Jelinek ---
Author: jakub
Date: Mon Oct 21 11:47:09 2019
New Revision: 277256
URL: https://gcc.gnu.org/viewcvs?rev=277256&root=gcc&view=rev
Log:
Backported from mainline
2019-10-04 Jakub Jelinek
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=91974
Richard Biener changed:
What|Removed |Added
Known to work||10.0
--- Comment #8 from Richard Biener
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=91974
--- Comment #7 from Jakub Jelinek ---
Author: jakub
Date: Fri Oct 4 06:54:05 2019
New Revision: 276562
URL: https://gcc.gnu.org/viewcvs?rev=276562&root=gcc&view=rev
Log:
PR c++/91974
* cp-gimplify.c (cp_gimplify_expr) : For
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=91974
Jakub Jelinek changed:
What|Removed |Added
Status|NEW |ASSIGNED
Assignee|unassigned a
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=91974
Jakub Jelinek changed:
What|Removed |Added
Status|UNCONFIRMED |NEW
Last reconfirmed|
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=91974
--- Comment #4 from Barry Revzin ---
Yes, sorry if that wasn't clear, this is with -std=c++17.
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=91974
--- Comment #3 from Andrew Pinski ---
Just to make sure, you are using -std=c++17 or -std=gnu++17 (or
-fstrong-eval-order)? Because it is not obvious from this report.
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=91974
--- Comment #2 from Barry Revzin ---
C++17 does change this rule. expr.call/8:
The postfix-expression is sequenced before each expression in the
expression-list and any default argument. The initialization of a parameter,
including every associa
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=91974
--- Comment #1 from Andrew Pinski ---
I dont think this is well defined. A call and its arguments are not sequence
points. Yes there is a sequence point between the assignment and 0 but nothing
else. Note c++17 does change the rules and I have
11 matches
Mail list logo
