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 target/60157] adding -mstrict-align for i386 and x86_64 architecture
Date: Mon, 08 Apr 2024 00:34:24 +0000 [thread overview]
Message-ID: <bug-60157-4-vlstlCmu8v@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-60157-4@http.gcc.gnu.org/bugzilla/>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=60157
Andrew Pinski <pinskia at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Keywords| |diagnostic
--- Comment #1 from Andrew Pinski <pinskia at gcc dot gnu.org> ---
>-mstrict-align
Will not help in this case really as GCC does not warn.
Note clang does warn with -mstrict-align though:
```
<source>:15:18: warning: field C within 'cond_mutex_t' is less aligned than
'pthread_cond_t' and is usually due to 'cond_mutex_t' being packed, which can
lead to unaligned accesses [-Wunaligned-access]
15 | pthread_cond_t C;
| ^
```
But I suspect GCC should warn even without strict alignment really.
prev parent reply other threads:[~2024-04-08 0:34 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-02-12 8:50 [Bug target/60157] New: " vinxxe at gmail dot com
2014-02-12 8:51 ` [Bug target/60157] " vinxxe at gmail dot com
2024-04-08 0:34 ` 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-60157-4-vlstlCmu8v@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: link
Be 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).