public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "pinskia at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug c++/61292] auto keyword to reference generates wrong alignment move (causing runtime segfault) Date: Wed, 28 Jul 2021 16:09:54 +0000 [thread overview] Message-ID: <bug-61292-4-MNRFvH4TVn@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-61292-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=61292 Andrew Pinski <pinskia at gcc dot gnu.org> changed: What |Removed |Added ---------------------------------------------------------------------------- Last reconfirmed| |2021-07-28 Status|UNCONFIRMED |NEW Summary|auto keyword to vector |auto keyword to reference |reference generates wrong |generates wrong alignment |alignment move (causing |move (causing runtime |runtime segfault) |segfault) Ever confirmed|0 |1 Keywords| |wrong-code --- Comment #4 from Andrew Pinski <pinskia at gcc dot gnu.org> --- This is unrelated to vector_size attribute even. Take: typedef float float32x4_t; typedef float __attribute__( ( aligned(1) ) ) float32x4a4_t; void add11(float32x4a4_t * x, float y, float32x4_t v) { auto & k1 = *(float32x4a4_t*)(x); auto & k2 = *(float32x4a4_t*)(x); k1 +=v; k2 += k1+v; } void add98(float32x4a4_t * x, float y, float32x4_t v) { float32x4a4_t & k1 = *(float32x4a4_t*)(x); float32x4a4_t & k2 = *(float32x4a4_t*)(x); k1 +=v; k2 += k1+v; } ------ CUT ----- With aarch64 at -O2 -mstrict-align, we get float loads/stores for add11 but correctly get the byte loads/stores for add98. Note I notice clang gets this wrong too.
prev parent reply other threads:[~2021-07-28 16:09 UTC|newest] Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top 2014-05-23 10:05 [Bug c++/61292] New: auto keyword to vector reference generates wrong alignment move vincenzo.innocente at cern dot ch 2014-05-25 12:19 ` [Bug c++/61292] auto keyword to vector reference generates wrong alignment move (causing runtime segfault) vincenzo.innocente at cern dot ch 2021-07-28 16:09 ` pinskia at gcc dot gnu.org [this message]
Reply instructions: You may reply publicly to this message via plain-text email using any one of the following methods: * Save the following mbox file, import it into your mail client, and reply-to-all from there: mbox Avoid top-posting and favor interleaved quoting: https://en.wikipedia.org/wiki/Posting_style#Interleaved_style * Reply using the --to, --cc, and --in-reply-to switches of git-send-email(1): git send-email \ --in-reply-to=bug-61292-4-MNRFvH4TVn@http.gcc.gnu.org/bugzilla/ \ --to=gcc-bugzilla@gcc.gnu.org \ --cc=gcc-bugs@gcc.gnu.org \ /path/to/YOUR_REPLY https://kernel.org/pub/software/scm/git/docs/git-send-email.html * If your mail client supports setting the In-Reply-To header via mailto: links, try the mailto: linkBe sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions for how to clone and mirror all data and code used for this inbox; as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).