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/103095] Option to force no overalignment
Date: Sun, 07 Nov 2021 16:07:54 +0000 [thread overview]
Message-ID: <bug-103095-4-MuKxGV9pv7@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-103095-4@http.gcc.gnu.org/bugzilla/>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=103095
Andrew Pinski <pinskia at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|REOPENED |UNCONFIRMED
Ever confirmed|1 |0
--- Comment #4 from Andrew Pinski <pinskia at gcc dot gnu.org> ---
(In reply to Tom de Vries from comment #3)
> In contrast, if we use -malign=abi and -fprecise-align, and the variable at
> runtime is found at address 0x8, we consider that the latter option is not
> obeyed.
The original issue referenced in this bug was really fixed with
-malign-data=abi.
The more complex issue here is that "over alignment" is something which might
be the just does not make sense as an option to be provided.
Stack will need be reunaligned at runtime, I have to wonder if this is even a
good thing to do and can be represented in dwarf2 ...
prev parent reply other threads:[~2021-11-07 16:07 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-11-05 10:30 [Bug other/103095] New: " vries at gcc dot gnu.org
2021-11-06 23:56 ` [Bug target/103095] " pinskia at gcc dot gnu.org
2021-11-07 0:05 ` pinskia at gcc dot gnu.org
2021-11-07 11:04 ` vries at gcc dot gnu.org
2021-11-07 16:07 ` 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-103095-4-MuKxGV9pv7@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).