From: Richard Biener <rguenther@suse.de>
To: FX <fxcoudert@gmail.com>
Cc: gcc-patches@gcc.gnu.org, Iain Sandoe <iain@sandoe.co.uk>
Subject: Re: [PATCH] middle-end/100786 - constant folding from incompatible alias
Date: Mon, 28 Mar 2022 08:34:15 +0200 (CEST) [thread overview]
Message-ID: <q790493n-r16r-85r1-7p2-1p7sq1634n4@fhfr.qr> (raw)
In-Reply-To: <00C2A5E0-35E0-4BEF-9780-69ADB0731F3F@gmail.com>
On Sat, 26 Mar 2022, FX wrote:
> Hi Richard,
>
> The patch for PR100786 introduced a testcase that systematically fails on darwin:
>
> FAIL: gcc.dg/torture/pr100786.c -O0 (test for excess errors)
> FAIL: gcc.dg/torture/pr100786.c -O1 (test for excess errors)
> FAIL: gcc.dg/torture/pr100786.c -O2 (test for excess errors)
> FAIL: gcc.dg/torture/pr100786.c -O2 -flto (test for excess errors)
> FAIL: gcc.dg/torture/pr100786.c -O2 -flto -flto-partition=none (test for excess errors)
> FAIL: gcc.dg/torture/pr100786.c -O3 -g (test for excess errors)
> FAIL: gcc.dg/torture/pr100786.c -Os (test for excess errors)
>
> see https://gcc.gnu.org/pipermail/gcc-testresults/2022-March/757882.html
>
> because
>
> pr100786.c:4:12: error: only weak aliases are supported in this configuration
> 4 | extern int b __attribute__((alias("a")));
> | ^
> pr100786.c:8:15: error: only weak aliases are supported in this configuration
> 8 | extern double b2 __attribute__((alias("a2")));
> | ^~
I'll add
/* { dg-require-alias "" } */
Richard.
next prev parent reply other threads:[~2022-03-28 6:34 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-03-26 16:54 FX
2022-03-28 6:34 ` Richard Biener [this message]
-- strict thread matches above, loose matches on Subject: below --
2022-01-20 13:58 Richard Biener
2022-01-20 14:02 ` Jakub Jelinek
2022-01-20 14:21 ` Richard Biener
2022-01-20 15:10 ` Richard Biener
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=q790493n-r16r-85r1-7p2-1p7sq1634n4@fhfr.qr \
--to=rguenther@suse.de \
--cc=fxcoudert@gmail.com \
--cc=gcc-patches@gcc.gnu.org \
--cc=iain@sandoe.co.uk \
/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).