public inbox for gcc-help@gcc.gnu.org
 help / color / mirror / Atom feed
From: Jonathan Wakely <jwakely.gcc@gmail.com>
To: Dennis Clarke <dclarke@blastwave.org>
Cc: gcc-help <gcc-help@gcc.gnu.org>
Subject: Re: on old Red Hat : 9.4.0 fails in stage3 bootstrap due to __asm__ ("ntp_gettimex") __THROW;
Date: Sun, 15 May 2022 21:45:57 +0100	[thread overview]
Message-ID: <CAH6eHdR=iUebbyx4eDGAihgM_6K_1=HG5dTFQvH-O_8goXNCJg@mail.gmail.com> (raw)
In-Reply-To: <436925d7-7fb7-c7f4-3e81-26db8b1f33cb@blastwave.org>

On Sun, 15 May 2022, 15:18 Dennis Clarke via Gcc-help, <gcc-help@gcc.gnu.org>
wrote:

>
> The last comment from Andrew Pinski in that bug report suggests it may
> be possible ( no promise ) to start over with --disable-libsanitiser and
> hope for the best.
>



If you spell it with a 'z' then yes.

>
> Dennis
>

  reply	other threads:[~2022-05-15 20:46 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-05-15 13:55 Dennis Clarke
2022-05-15 14:17 ` Dennis Clarke
2022-05-15 20:45   ` Jonathan Wakely [this message]
2022-05-15 21:16     ` Dennis Clarke

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='CAH6eHdR=iUebbyx4eDGAihgM_6K_1=HG5dTFQvH-O_8goXNCJg@mail.gmail.com' \
    --to=jwakely.gcc@gmail.com \
    --cc=dclarke@blastwave.org \
    --cc=gcc-help@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).