This is the mail archive of the gcc-bugs@gcc.gnu.org mailing list for the GCC project.


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]
Other format: [Raw text]

[Bug target/80837] [7/8 regression] x86 accessing a member of a 16-byte atomic object generates terrible code: splitting/merging the bytes


https://gcc.gnu.org/bugzilla/show_bug.cgi?id=80837

Jakub Jelinek <jakub at gcc dot gnu.org> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|NEW                         |RESOLVED
         Resolution|---                         |DUPLICATE

--- Comment #9 from Jakub Jelinek <jakub at gcc dot gnu.org> ---
Actually managed to reproduce today using godbolt's -E output.
This is something that got fixed with r247104 on the trunk and backported
to 7.2 as r248724.  So I believe this is fixed.  The choice to emit
__atomic_load_16 calls is intentional, see the overlong thread about it from
the last week or so on gcc at gcc.gnu.org mailing list.

*** This bug has been marked as a duplicate of bug 80293 ***

Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]