https://gcc.gnu.org/bugzilla/show_bug.cgi?id=101378
Jakub Jelinek changed:
What|Removed |Added
Resolution|--- |FIXED
Status|NEW
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=101378
--- Comment #14 from CVS Commits ---
The releases/gcc-9 branch has been updated by Jakub Jelinek
:
https://gcc.gnu.org/g:4b14a4af62368e8b4892c195e4af80be8893bb0b
commit r9-10108-g4b14a4af62368e8b4892c195e4af80be8893bb0b
Author: Jakub Jelinek
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=101378
--- Comment #13 from CVS Commits ---
The releases/gcc-10 branch has been updated by Jakub Jelinek
:
https://gcc.gnu.org/g:b7f30978be64fb7029698c8a3c4f4435d32f8097
commit r10-10652-gb7f30978be64fb7029698c8a3c4f4435d32f8097
Author: Jakub Jelinek
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=101378
--- Comment #12 from CVS Commits ---
The releases/gcc-11 branch has been updated by Jakub Jelinek
:
https://gcc.gnu.org/g:c479d98137fb589718570258547c6bea4f27d1d5
commit r11-9330-gc479d98137fb589718570258547c6bea4f27d1d5
Author: Jakub Jelinek
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=101378
--- Comment #11 from CVS Commits ---
The master branch has been updated by Jakub Jelinek :
https://gcc.gnu.org/g:10db7573014008ff867098206f51012d501ab57b
commit r12-5148-g10db7573014008ff867098206f51012d501ab57b
Author: Jakub Jelinek
Date:
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=101378
--- Comment #10 from Pedro Alves ---
I've now compared GDB testsuite runs with current GCC, unpatched vs patched, no
regressions.
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=101378
--- Comment #9 from Pedro Alves ---
> 2021-11-09 Jakub Jelinek
>
> PR debug/101378
> * dwarf2out.c (field_byte_offset): Do the PCC_BITFIELD_TYPE_MATTERS
> handling only for DECL_BIT_FIELD decls.
>
> ...
>
> fixes this for
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=101378
--- Comment #8 from Pedro Alves ---
Thank you, I missed the "same type" constraint. It's also mentioned at
https://en.cppreference.com/w/cpp/language/attributes/no_unique_address .
Indeed, if I use distinct empty types, GCC and Clang lay them
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=101378
--- Comment #7 from Jakub Jelinek ---
I must say I don't understand why we do that PCC_BITFIELD_TYPE_MATTERS stuff in
dwarf2out.c (field_byte_offset) for non-bitfields, I don't understand why
byte_position (decl) wouldn't work just fine. After
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=101378
Richard Biener changed:
What|Removed |Added
Last reconfirmed||2021-11-09
Ever confirmed|0
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=101378
--- Comment #5 from Jonathan Wakely ---
... and if the type is visible outside a single translation unit, then it needs
to follow the layout mandated by the ABI anyway, or it would violate the
One-Definition Rule.
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=101378
--- Comment #4 from Jonathan Wakely ---
The C++ standard forbids two objects of the same type having the same address.
That is true for the empty base-class optimization and it's true for
[[no_unique_address]].
[intro.object]
> Two objects wit
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=101378
--- Comment #3 from Pedro Alves ---
BTW, I found it curious that empty2 and empty3 get their own addresses, even at
run time, when they could have all been squashed to the same address. I.e.,
e.g., this ends up with sizeof == 3, when it could h
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=101378
Pedro Alves changed:
What|Removed |Added
CC||alves.ped at gmail dot com
--- Comment #2
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=101378
--- Comment #1 from Simon Marchi ---
I bisected, it started with:
libstdc++: Remove inheritance from elements in std::tuple
91e6226f880b048275a7ceedef716e159c7cefd9
So it's likely related to the use of [[no_unique_address]].
Relevant thread o
15 matches
Mail list logo
