public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "pault at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug fortran/94386] [10 Regression] FAIL: gfortran.dg/pr93365.f90
Date: Tue, 31 Mar 2020 08:42:06 +0000 [thread overview]
Message-ID: <bug-94386-4-6fBuykcTSl@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-94386-4@http.gcc.gnu.org/bugzilla/>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=94386
--- Comment #9 from Paul Thomas <pault at gcc dot gnu.org> ---
> > These were both clean builds run on a powerpc64 power8 LE machine.
>
> The patch committed to fix(?) PR94246 reverted the code that fixed
> PR93665 and PR93600 without removing the now failing testcases and
> re-opening the now unfixed PR93665 and PR93600. %len and %kind
> need to be special cased. See, Oh, I don't know maybe the removed
> comments in the diff.
Aaaah! OK, this a sign of my complete and utter incompetence with using git.
Could somebody please point me to the prescription for fixing this?
g:7d57570b0658b8c1b8a97dafa53dfd4ab4bd3f65, r10-7444 points to my intended
commit and nothing else.
I would also like to know how I could have done this since git normally
complains vociferously if I try to violate HEAD by doing things in the wrong
order.
Est mea maxima culpa, sed nescio quomodo me fecit ...
Paul
next prev parent reply other threads:[~2020-03-31 8:42 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-03-29 12:28 [Bug fortran/94386] New: " hjl.tools at gmail dot com
2020-03-29 14:42 ` [Bug fortran/94386] " tkoenig at gcc dot gnu.org
2020-03-29 17:30 ` marxin at gcc dot gnu.org
2020-03-29 18:10 ` pault at gcc dot gnu.org
2020-03-29 19:17 ` seurer at linux dot vnet.ibm.com
2020-03-30 8:14 ` rguenth at gcc dot gnu.org
2020-03-30 18:09 ` pault at gcc dot gnu.org
2020-03-30 19:45 ` seurer at linux dot vnet.ibm.com
2020-03-30 20:36 ` burnus at gcc dot gnu.org
2020-03-31 2:04 ` kargl at gcc dot gnu.org
2020-03-31 8:42 ` pault at gcc dot gnu.org [this message]
2020-04-01 7:53 ` rguenth at gcc dot gnu.org
2020-04-01 8:46 ` jakub at gcc dot gnu.org
2020-04-01 9:03 ` markeggleston at gcc dot gnu.org
2020-04-01 11:51 ` cvs-commit at gcc dot gnu.org
2020-04-01 11:59 ` markeggleston at gcc dot gnu.org
2020-04-01 16:51 ` pault 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-94386-4-6fBuykcTSl@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).