From: Jakub Jelinek <jakub@redhat.com>
To: Andreas Krebbel <krebbel@linux.vnet.ibm.com>
Cc: Martin Sebor <msebor@gmail.com>,
Gcc Patch List <gcc-patches@gcc.gnu.org>
Subject: Re: [PATCH 1/3] improve detection of attribute conflicts (PR 81544)
Date: Thu, 05 Apr 2018 10:35:00 -0000 [thread overview]
Message-ID: <20180405074213.GV8577@tucnak> (raw)
In-Reply-To: <f8a6fae9-2be5-f287-85bb-60061c9e8e8a@linux.vnet.ibm.com>
On Thu, Apr 05, 2018 at 09:01:02AM +0200, Andreas Krebbel wrote:
> > Wouldn't it be better to just use aligned (8) and aligned (16) instead of
> > aligned (4) and aligned (8)?
>
> aligned (8) does not trigger the warning anymore. Neither on s390 nor on x86. I don't think there
> is a way to ever see this warning on s390. Values >= 8 would be ok (no warning, no error) and
> values < 8 would trigger the error but not the warning.
Your patch is ok then.
Jakub
next prev parent reply other threads:[~2018-04-05 10:35 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-08-08 16:14 Martin Sebor
2017-08-09 11:53 ` Marek Polacek
2017-08-09 14:19 ` Martin Sebor
2017-08-09 17:13 ` Joseph Myers
2017-08-09 19:26 ` Martin Sebor
2017-08-09 20:47 ` Joseph Myers
2017-08-10 4:47 ` Martin Sebor
2017-08-10 23:51 ` Joseph Myers
2017-08-11 16:46 ` Martin Sebor
2017-08-11 16:49 ` Joseph Myers
2017-08-17 18:23 ` Martin Sebor
2017-08-24 21:10 ` Martin Sebor
2017-08-29 5:21 ` Martin Sebor
2017-09-06 23:30 ` Joseph Myers
2017-09-19 19:48 ` Martin Sebor
2017-09-19 21:00 ` Joseph Myers
2017-09-20 18:04 ` Martin Sebor
2017-10-02 22:24 ` Jeff Law
2018-04-04 16:16 ` Andreas Krebbel
2018-04-04 16:51 ` Andreas Krebbel
2018-04-04 17:18 ` Martin Sebor
2018-04-04 17:35 ` Jakub Jelinek
2018-04-05 7:01 ` Andreas Krebbel
2018-04-05 10:35 ` Jakub Jelinek [this message]
2017-09-12 17:06 ` Jeff Law
2017-09-19 20:00 ` Martin Sebor
2017-09-12 15:44 ` Jeff Law
2017-09-12 15:50 ` Jeff Law
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=20180405074213.GV8577@tucnak \
--to=jakub@redhat.com \
--cc=gcc-patches@gcc.gnu.org \
--cc=krebbel@linux.vnet.ibm.com \
--cc=msebor@gmail.com \
/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).