public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "anlauf at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug libfortran/96890] Wrong answer with intrinsic IALL
Date: Thu, 03 Sep 2020 15:07:12 +0000 [thread overview]
Message-ID: <bug-96890-4-FFqeB1fDnA@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-96890-4@http.gcc.gnu.org/bugzilla/>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=96890
--- Comment #5 from anlauf at gcc dot gnu.org ---
(In reply to Steve Kargl from comment #4)
> Ping Thomas. I recall seeing that he recently was
> asking about --enable-maintainer-mode in a git
> world.
Hacking the Makfile in x86_64-pc-linux-gnu/libgfortran/Makefile
and manually activating the dependency
$(i_iall_c): m4/iall.m4 $(I_M4_DEPS1)
$(M4) -Dfile=$@ -I$(srcdir)/m4 iall.m4 > $@
does the job, too.
Ugh.
next prev parent reply other threads:[~2020-09-03 15:07 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-09-02 1:19 [Bug fortran/96890] New: " zhen.xu@compiler-dev.com
2020-09-02 21:17 ` [Bug libfortran/96890] " anlauf at gcc dot gnu.org
2020-09-03 4:56 ` kargl at gcc dot gnu.org
2020-09-03 14:32 ` anlauf at gcc dot gnu.org
2020-09-03 14:40 ` sgk at troutmask dot apl.washington.edu
2020-09-03 15:07 ` anlauf at gcc dot gnu.org [this message]
2020-09-03 18:33 ` cvs-commit at gcc dot gnu.org
2020-09-03 18:51 ` anlauf at gcc dot gnu.org
2020-09-08 20:20 ` cvs-commit at gcc dot gnu.org
2020-09-09 19:39 ` cvs-commit at gcc dot gnu.org
2020-09-09 19:43 ` cvs-commit at gcc dot gnu.org
2020-09-09 19:44 ` anlauf 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-96890-4-FFqeB1fDnA@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).