public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "tkoenig at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug libfortran/95418] [11 Regression] Static assert going off on MinGW
Date: Sun, 31 May 2020 22:07:48 +0000 [thread overview]
Message-ID: <bug-95418-4-qh3UBJFJqf@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-95418-4@http.gcc.gnu.org/bugzilla/>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=95418
--- Comment #9 from Thomas Koenig <tkoenig at gcc dot gnu.org> ---
(In reply to Uroš Bizjak from comment #6)
> Thomas,
>
> Contrary to my other libgfortran contribution, I was under the impression
> that the patch touches only deep architectural details of the x87 chip, and
> should be (and in fact is) independent of libgfortran implementation.
Well, that's what https://gcc.gnu.org/fortran/ states - please copy
us in in the future. It makes more sense to have a simpler rule
than to make exceptions for specific subdirectories. (You can, of
course, also commit a change as "obvious and simple", but we'd
also appreciate a note about this).
next prev parent reply other threads:[~2020-05-31 22:07 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-05-29 14:22 [Bug libfortran/95418] New: " markus.boeck02 at gmail dot com
2020-05-30 20:17 ` [Bug libfortran/95418] " anlauf at gcc dot gnu.org
2020-05-31 9:07 ` markus.boeck02 at gmail dot com
2020-05-31 18:07 ` [Bug libfortran/95418] [11 Regression] " tkoenig at gcc dot gnu.org
2020-05-31 18:07 ` tkoenig at gcc dot gnu.org
2020-05-31 18:42 ` pinskia at gcc dot gnu.org
2020-05-31 18:55 ` pinskia at gcc dot gnu.org
2020-05-31 19:34 ` ubizjak at gmail dot com
2020-05-31 20:06 ` ubizjak at gmail dot com
2020-05-31 21:32 ` markus.boeck02 at gmail dot com
2020-05-31 22:07 ` tkoenig at gcc dot gnu.org [this message]
2020-06-01 20:29 ` cvs-commit at gcc dot gnu.org
2020-06-01 20:35 ` ubizjak at gmail dot com
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-95418-4-qh3UBJFJqf@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).