public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "dkm at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug target/114910] can't build a c6x cross compiler
Date: Fri, 03 May 2024 11:53:35 +0000	[thread overview]
Message-ID: <bug-114910-4-5n7Vm4IbBl@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-114910-4@http.gcc.gnu.org/bugzilla/>

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

--- Comment #9 from Marc Poulhiès <dkm at gcc dot gnu.org> ---
Yes, sorry I should have added that in my original message (I did mention the
commit on IRC). This is the commit that introduces the hardcfr.c file that is
miscompiled. The error may be latent and bisecting should probably run the
above command with a copy of a preprocessed hardcfr.c ?

      parent reply	other threads:[~2024-05-03 11:53 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-05-01 16:24 [Bug target/114910] New: " dkm at gcc dot gnu.org
2024-05-01 17:04 ` [Bug target/114910] " pinskia at gcc dot gnu.org
2024-05-01 22:46 ` pinskia at gcc dot gnu.org
2024-05-01 22:51 ` pinskia at gcc dot gnu.org
2024-05-02  7:19 ` dkm at gcc dot gnu.org
2024-05-02 13:22 ` mikpelinux at gmail dot com
2024-05-02 17:00 ` dkm at gcc dot gnu.org
2024-05-02 23:52 ` mikpelinux at gmail dot com
2024-05-03 11:12 ` mikpelinux at gmail dot com
2024-05-03 11:53 ` dkm at gcc dot gnu.org [this message]

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-114910-4-5n7Vm4IbBl@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).