https://gcc.gnu.org/bugzilla/show_bug.cgi?id=32911
--- Comment #8 from Eric Gallager ---
It might also be worth comparing against the attributes [[unsequenced]] and
[[reproducible]] proposed for the C standard:
https://www.open-std.org/jtc1/sc22/wg14/www/docs/n2956.htm
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=32911
Trass3r changed:
What|Removed |Added
CC||trass3r at gmail dot com
--- Comment #7 from T
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=32911
Matthew Wilcox changed:
What|Removed |Added
CC||matthew at wil dot cx
--- Comment #6 fr
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=32911
--- Comment #5 from Philip Withnall ---
Bug filed against Clang with the same request here:
https://bugs.llvm.org/show_bug.cgi?id=34600
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=32911
Jan Hubicka changed:
What|Removed |Added
CC||hubicka at gcc dot gnu.org
--- Comment #4 f
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=32911
--- Comment #3 from Jan Hubicka 2012-05-15 15:57:29 UTC
---
Note that I was thinking of similar attribute for C++ iostream initialization
code.
Currently every unit including iostream gets a call to the iostream
constructor. With LTO
we merge the
Note that I was thinking of similar attribute for C++ iostream initialization
code.
Currently every unit including iostream gets a call to the iostream
constructor. With LTO
we merge the constructors together and get _alot_ of redundant calls to the
construction
code. Declaring that only first
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=32911
Colin Walters changed:
What|Removed |Added
CC||walters at verbum dot org
--- Comment #2
--- Comment #1 from pinskia at gcc dot gnu dot org 2007-07-27 09:35 ---
The Java front-end has the same problem.
--
pinskia at gcc dot gnu dot org changed:
What|Removed |Added