https://gcc.gnu.org/bugzilla/show_bug.cgi?id=78868
--- Comment #2 from Andrew Pinski ---
Note C++17 does specify this more now IIRC.
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=78868
--- Comment #3 from Vlad Krasnov ---
I though that since va_arg is defined as a macro, it should be evaluated in
order.
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=78868
--- Comment #4 from Andrew Pinski ---
It is the call to printf and the order of evaluation of its arguments. That is
take:
F (g (), h ());
g or h could be called first. The same thing is true here.
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=78516
--- Comment #15 from Vladimir Makarov ---
(In reply to Peter Bergner from comment #13)
> (In reply to Vladimir Makarov from comment #11)
> > Created attachment 40372 [details]
> > The proposed patch
>
> Agreed your additions to my change looks g
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=78516
--- Comment #16 from Peter Bergner ---
(In reply to Vladimir Makarov from comment #15)
> Sorry, I applied your changes manually and did a typo. The line
>
> SET_SRC (curr_insn_set) = new_reg;
>
> should be removed.
>
> I tested this patch wit
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=78745
--- Comment #3 from Frederic Marchal ---
One more truncated entry in gcc/config/aarch64/aarch64.opt at line 154.
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=78867
--- Comment #2 from Janne Blomqvist ---
(In reply to Dominique d'Humieres from comment #1)
> This seems to be a regression between revisions r243624 (2016-12-13,
> compiles) and r243765 (2016-12-16, ICE with -m32 or -m64).
Thanks for quickly nar
101 - 107 of 107 matches
Mail list logo
