From: "Maciej W. Rozycki" <macro@orcam.me.uk>
To: Alexandre Oliva <oliva@adacore.com>
Cc: Segher Boessenkool <segher@kernel.crashing.org>,
gcc-patches@gcc.gnu.org, dje.gcc@gmail.com
Subject: Re: [PATCH v2] [PR100106] Reject unaligned subregs when strict alignment is required
Date: Wed, 12 Jun 2024 13:39:52 +0100 (BST) [thread overview]
Message-ID: <alpine.DEB.2.21.2406111607210.9248@angie.orcam.me.uk> (raw)
In-Reply-To: <orfslnfkm1.fsf_-_@lxoliva.fsfla.org>
On Thu, 5 May 2022, Alexandre Oliva via Gcc-patches wrote:
> [PR100106] Reject unaligned subregs when strict alignment is required
>
> From: Alexandre Oliva <oliva@adacore.com>
>
> The testcase for pr100106, compiled with optimization for 32-bit
> powerpc -mcpu=604 with -mstrict-align expands the initialization of a
> union from a float _Complex value into a load from an SCmode
> constant pool entry, aligned to 4 bytes, into a DImode pseudo,
> requiring 8-byte alignment.
This has regressed building the `alpha-linux-gnu' target, in libada, as
from commit d6b756447cd5 including GCC 14 and up to current GCC 15 trunk:
during RTL pass: ira
+===========================GNAT BUG DETECTED==============================+
| 15.0.0 20240610 (experimental) (alpha-linux-gnu) GCC error: |
| in gen_rtx_SUBREG, at emit-rtl.cc:1032 |
| Error detected around g-debpoo.adb:1896:8 |
| Compiling g-debpoo.adb |
| Please submit a bug report; see https://gcc.gnu.org/bugs/ . |
| Use a subject line meaningful to you and us to track the bug. |
| Include the entire contents of this bug box in the report. |
| Include the exact command that you entered. |
| Also include sources listed below. |
+==========================================================================+
I have filed PR #115459.
Maciej
next prev parent reply other threads:[~2024-06-12 12:39 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-05-05 6:52 [PATCH] " Alexandre Oliva
2022-05-05 7:59 ` Richard Sandiford
2022-05-05 13:50 ` Segher Boessenkool
2022-05-06 10:57 ` [PATCH v2 2/2] " Alexandre Oliva
2022-05-09 8:09 ` Richard Sandiford
2022-05-05 14:33 ` [PATCH] " Segher Boessenkool
2022-05-06 2:41 ` [PATCH v2] " Alexandre Oliva
2022-07-09 17:14 ` Jeff Law
2023-05-24 5:39 ` Alexandre Oliva
2023-05-24 9:04 ` Richard Biener
2024-06-12 12:39 ` Maciej W. Rozycki [this message]
2024-06-13 7:36 ` [PATCH] [alpha] adjust MEM alignment for block move [PR115459] (was: Re: [PATCH v2] [PR100106] Reject unaligned subregs when strict alignment is required) Alexandre Oliva
2024-06-13 11:49 ` Maciej W. Rozycki
2024-06-13 15:21 ` Joseph Myers
2024-06-18 9:59 ` Maciej W. Rozycki
2022-05-06 18:04 ` [PATCH] [PR100106] Reject unaligned subregs when strict alignment is required Vladimir Makarov
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=alpine.DEB.2.21.2406111607210.9248@angie.orcam.me.uk \
--to=macro@orcam.me.uk \
--cc=dje.gcc@gmail.com \
--cc=gcc-patches@gcc.gnu.org \
--cc=oliva@adacore.com \
--cc=segher@kernel.crashing.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).