From: Jonathan Wakely <jwakely.gcc@gmail.com>
To: Paul Koning <paulkoning@comcast.net>
Cc: Alexander Monakov <amonakov@ispras.ru>,
"gcc@gcc.gnu.org" <gcc@gcc.gnu.org>
Subject: Re: asking for __attribute__((aligned()) clarification
Date: Wed, 21 Aug 2019 17:35:00 -0000 [thread overview]
Message-ID: <CAH6eHdQWiSujtQx=rPQoJ5ZL7FxK9DY4wFrEqBtkJ5yBC11ydg@mail.gmail.com> (raw)
In-Reply-To: <DC06E8B3-EA12-47B2-B653-39241A123868@comcast.net>
On Wed, 21 Aug 2019 at 17:50, Paul Koning <paulkoning@comcast.net> wrote:
>
>
>
> > On Aug 21, 2019, at 10:57 AM, Alexander Monakov <amonakov@ispras.ru> wrote:
> >
> > On Wed, 21 Aug 2019, Paul Koning wrote:
> >
> >> I agree, but if the new approach generates a warning for code that was written
> >> to the old rules, that would be unfortunate.
> >
> > FWIW I don't know which GCC versions accepted 'packed' on a scalar type.
>
> That wasn't what I meant; I was talking about the packed and aligned attributes on struct members. I thought you were saying that ((packed,aligned(2))) is now a warning. That doesn't appear to be the case, though; it's accepted without complaint as it always was.
Right, nobody's suggesting that should be a warning. The warning is
for trying to pack a scalar variable, which is (and always was)
meaningless.
prev parent reply other threads:[~2019-08-21 17:35 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-08-19 12:46 "Markus Fröschle"
2019-08-19 13:57 ` Paul Koning
2019-08-19 14:01 ` Richard Earnshaw (lists)
2019-08-19 14:08 ` Alexander Monakov
2019-08-19 14:12 ` Paul Koning
2019-08-20 5:46 ` Aw: " "Markus Fröschle"
2019-08-21 14:29 ` Alexander Monakov
2019-08-21 14:32 ` Paul Koning
2019-08-21 14:58 ` Alexander Monakov
2019-08-21 16:50 ` Paul Koning
2019-08-21 17:35 ` Jonathan Wakely [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='CAH6eHdQWiSujtQx=rPQoJ5ZL7FxK9DY4wFrEqBtkJ5yBC11ydg@mail.gmail.com' \
--to=jwakely.gcc@gmail.com \
--cc=amonakov@ispras.ru \
--cc=gcc@gcc.gnu.org \
--cc=paulkoning@comcast.net \
/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).