From: FX Coudert <fxcoudert@gmail.com>
To: Iain Sandoe <iains.gcc@gmail.com>
Cc: GCC Patches <gcc-patches@gcc.gnu.org>,
Jakub Jelinek <jakub@redhat.com>,
jose.marchesi@oracle.com
Subject: Re: [r14-5930 Regression] FAIL: gcc.c-torture/compile/libcall-2.c -Os (test for excess errors) on Linux/x86_64
Date: Sat, 2 Dec 2023 10:04:23 +0100 [thread overview]
Message-ID: <3025E477-2E50-4A30-8AF9-4A08CAC94166@gmail.com> (raw)
In-Reply-To: <F80650CD-B547-4FCC-8040-9590D14D26D7@gmail.com>
> mcmodel=large s not supported (yet) on any Darwin arch [PR90698], so the test needs skipping or xfailing, I think (either way with a reference to the PR).
Pushed as https://gcc.gnu.org/git/?p=gcc.git;a=commitdiff;h=b74981b5cf32ebf4bfffd25e7174b5c80243447a
FX
next prev parent reply other threads:[~2023-12-02 9:04 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-12-01 13:55 FX Coudert
2023-12-01 14:38 ` Iain Sandoe
2023-12-02 9:04 ` FX Coudert [this message]
2023-12-04 8:40 ` Jose E. Marchesi
2023-12-11 8:23 ` FX Coudert
-- strict thread matches above, loose matches on Subject: below --
2023-11-28 23:19 haochen.jiang
2023-11-29 6:51 ` Jose E. Marchesi
2023-11-29 7:51 ` Jakub Jelinek
2023-11-29 8:20 ` Jose E. Marchesi
2023-11-29 8:22 ` Jakub Jelinek
2023-11-29 8:32 ` Jose E. Marchesi
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=3025E477-2E50-4A30-8AF9-4A08CAC94166@gmail.com \
--to=fxcoudert@gmail.com \
--cc=gcc-patches@gcc.gnu.org \
--cc=iains.gcc@gmail.com \
--cc=jakub@redhat.com \
--cc=jose.marchesi@oracle.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).