public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "ro at CeBiTec dot Uni-Bielefeld.DE" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug libfortran/104006] [12 regression] power-ieee128 merge breaks Solaris build
Date: Thu, 13 Jan 2022 14:30:22 +0000	[thread overview]
Message-ID: <bug-104006-4-ASKJST3poM@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-104006-4@http.gcc.gnu.org/bugzilla/>

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

--- Comment #7 from ro at CeBiTec dot Uni-Bielefeld.DE <ro at CeBiTec dot Uni-Bielefeld.DE> ---
> --- Comment #5 from Jakub Jelinek <jakub at gcc dot gnu.org> ---
> (In reply to ro@CeBiTec.Uni-Bielefeld.DE from comment #3)
>> Really strange.  If kinds.h were missing completely at that point, I'd
>> expect gcc message to that effect, that's why I suspected the header
>> being incomplete instead.
>
> You can hit the case where kinds.h has been created already but nothing has
> been stored to it yet, mk-kinds-h.sh script is invoked with > kinds.h so that
> is created immediately kinds.h goal starts, but does some compilations first
> before it echoes something to stdout.

Which suggests kinds.h (and other files generated in a similar way)
should use move-if-change to avoid this.

make kinds.h takes about 1.2s on my sparc box, so there's a considerable
window the file could be incomplete.

  parent reply	other threads:[~2022-01-13 14:30 UTC|newest]

Thread overview: 30+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-01-13 12:39 [Bug libfortran/104006] New: " ro at gcc dot gnu.org
2022-01-13 12:40 ` [Bug libfortran/104006] " ro at gcc dot gnu.org
2022-01-13 13:17 ` jakub at gcc dot gnu.org
2022-01-13 13:20 ` jakub at gcc dot gnu.org
2022-01-13 13:43 ` ro at CeBiTec dot Uni-Bielefeld.DE
2022-01-13 14:01 ` jakub at gcc dot gnu.org
2022-01-13 14:04 ` jakub at gcc dot gnu.org
2022-01-13 14:28 ` ro at CeBiTec dot Uni-Bielefeld.DE
2022-01-13 14:30 ` ro at CeBiTec dot Uni-Bielefeld.DE [this message]
2022-01-13 14:37 ` jakub at gcc dot gnu.org
2022-01-13 14:52 ` jakub at gcc dot gnu.org
2022-01-13 15:02 ` ro at CeBiTec dot Uni-Bielefeld.DE
2022-01-13 15:07 ` jakub at gcc dot gnu.org
2022-01-13 15:13 ` ro at CeBiTec dot Uni-Bielefeld.DE
2022-01-13 16:39 ` jakub at gcc dot gnu.org
2022-01-13 16:42 ` jakub at gcc dot gnu.org
2022-01-13 16:50 ` cvs-commit at gcc dot gnu.org
2022-01-13 17:26 ` jakub at gcc dot gnu.org
2022-01-13 18:32 ` ro at CeBiTec dot Uni-Bielefeld.DE
2022-01-13 18:39 ` jakub at gcc dot gnu.org
2022-01-13 21:26 ` ro at CeBiTec dot Uni-Bielefeld.DE
2022-01-13 21:27 ` ro at gcc dot gnu.org
2022-01-13 21:39 ` jakub at gcc dot gnu.org
2022-01-13 21:52 ` ro at CeBiTec dot Uni-Bielefeld.DE
2022-01-13 22:39 ` jakub at gcc dot gnu.org
2022-01-13 22:42 ` jakub at gcc dot gnu.org
2022-01-13 22:52 ` ro at CeBiTec dot Uni-Bielefeld.DE
2022-01-14  6:45 ` ro at CeBiTec dot Uni-Bielefeld.DE
2022-01-14 11:19 ` cvs-commit at gcc dot gnu.org
2022-01-15 12:22 ` jakub 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-104006-4-ASKJST3poM@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).