public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "nightstrike at gmail dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug testsuite/108150] gcc.dg/attr-aligned.c fails with incorrect max alignment
Date: Tue, 27 Dec 2022 22:43:51 +0000	[thread overview]
Message-ID: <bug-108150-4-11b1teKDt5@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-108150-4@http.gcc.gnu.org/bugzilla/>

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=108150

nightstrike <nightstrike at gmail dot com> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |10walls at gmail dot com

--- Comment #2 from nightstrike <nightstrike at gmail dot com> ---
It occurs to me, if GCC already internally knows the max alignment (since it's
outputting it in the warning message), why do we need to have such complicated
preprocessor magic to guess at what the alignment is?  Would it be easier to
have GCC just define __GCC_MAX_ALIGNMENT__ or something similar for all
targets, and then use that in the test?

  parent reply	other threads:[~2022-12-27 22:43 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-12-17  1:40 [Bug c/108150] New: " nightstrike at gmail dot com
2022-12-19  8:19 ` [Bug testsuite/108150] " nightstrike at gmail dot com
2022-12-27 22:43 ` nightstrike at gmail dot com [this message]
2023-01-08  1:33 ` 10walls at gmail dot com
2023-01-28 16:32 ` cvs-commit at gcc dot gnu.org

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-108150-4-11b1teKDt5@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).