[Bug c/61739] __builtin_printf optimization conflicts with POSIX semantics

2014-07-11 Thread bugdal at aerifal dot cx
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=61739 --- Comment #5 from Rich Felker --- I reopened this, but now that I'm reporting a new symptom that's independent of the original symptom, I'm wondering whether I should file a separate bug report for it, or continue the issue under this original

[Bug c/61739] __builtin_printf optimization conflicts with POSIX semantics

2014-07-08 Thread bugdal at aerifal dot cx
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=61739 --- Comment #4 from Rich Felker --- Sorry, that should be: printf(""); printf("%d\n", fwide(stdout, 0));

[Bug c/61739] __builtin_printf optimization conflicts with POSIX semantics

2014-07-08 Thread bugdal at aerifal dot cx
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=61739 Rich Felker changed: What|Removed |Added Status|RESOLVED|UNCONFIRMED Resolution|INVALID

[Bug c/61739] __builtin_printf optimization conflicts with POSIX semantics

2014-07-08 Thread rguenth at gcc dot gnu.org
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=61739 Richard Biener changed: What|Removed |Added Status|UNCONFIRMED |RESOLVED Resolution|---

[Bug c/61739] __builtin_printf optimization conflicts with POSIX semantics

2014-07-08 Thread sch...@linux-m68k.org
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=61739 --- Comment #1 from Andreas Schwab --- Since printf("") does not need to obtain ownership of stdout there is no conflict here. There is no requirement that it *must* obtain ownership even if not needed.