public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "slyfox at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug target/107064] gcc/config/t-i386 depends are incomplete: /gcc/config/i386/i386-builtins.h:25:10:      fatal error: i386-builtin-types.inc: No such file or directory
Date: Mon, 03 Oct 2022 21:00:51 +0000	[thread overview]
Message-ID: <bug-107064-4-yY50sgul9h@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-107064-4@http.gcc.gnu.org/bugzilla/>

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

Sergei Trofimovich <slyfox at gcc dot gnu.org> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|UNCONFIRMED                 |ASSIGNED
   Last reconfirmed|                            |2022-10-03
     Ever confirmed|0                           |1
           Assignee|unassigned at gcc dot gnu.org      |slyfox at gcc dot gnu.org

--- Comment #2 from Sergei Trofimovich <slyfox at gcc dot gnu.org> ---
Pushed to master as r13-3048-gef3165736d9daa (forgot to add PR reference to the
commit, will add to backports).

  parent reply	other threads:[~2022-10-03 21:00 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-09-28  6:26 [Bug other/107064] New: " slyfox at gcc dot gnu.org
2022-09-28  6:28 ` [Bug other/107064] " slyfox at gcc dot gnu.org
2022-10-03 21:00 ` slyfox at gcc dot gnu.org [this message]
2022-10-03 21:07 ` [Bug target/107064] " cvs-commit at gcc dot gnu.org
2022-10-03 21:07 ` cvs-commit at gcc dot gnu.org
2022-10-03 21:08 ` cvs-commit at gcc dot gnu.org
2022-10-03 21:09 ` slyfox at gcc dot gnu.org

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-107064-4-yY50sgul9h@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).