public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "kargl at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug fortran/52279] Fortran translation issues
Date: Thu, 02 Jul 2020 15:31:37 +0000 [thread overview]
Message-ID: <bug-52279-4-iRvhwA4i3M@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-52279-4@http.gcc.gnu.org/bugzilla/>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=52279
--- Comment #6 from kargl at gcc dot gnu.org ---
(In reply to markeggleston from comment #5)
> (In reply to markeggleston from comment #4)
> > Regarding comment 2.
> >
> > Using -fallow-invalid-boz results in an ICE. I'll create a new PR.
>
> Not true, tried it on the wrong file and jumped to the wrong conclusion.
This is wrong.
index 26ea01f..8ecf4ff 100644 (file)
--- a/gcc/fortran/check.c
+++ b/gcc/fortran/check.c
@@ -67,7 +67,7 @@ gfc_invalid_boz (const char *msg, locus *loc)
return false;
}
- const char hint[] = " [see %<-fno-allow-invalid-boz%>]";
+ const char *hint = " [see %<-fno-allow-invalid-boz%>]";
size_t len = strlen (msg) + strlen (hint) + 1;
char *msg2 = (char *) alloca (len);
strcpy (msg2, msg);
There is no -fno-allow-invalid-boz option. The option is
-fallow-invalid-boz. fortan/lang.opt defines the options
with the RejectNegative annotation.
next prev parent reply other threads:[~2020-07-02 15:31 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-02-16 14:29 [Bug fortran/52279] New: Fortran translation issues issues burnus at gcc dot gnu.org
2013-06-29 22:24 ` [Bug fortran/52279] " dominiq at lps dot ens.fr
2020-07-01 16:08 ` [Bug fortran/52279] Fortran translation issues cvs-commit at gcc dot gnu.org
2020-07-01 21:39 ` kargl at gcc dot gnu.org
2020-07-02 10:05 ` cvs-commit at gcc dot gnu.org
2020-07-02 10:14 ` markeggleston at gcc dot gnu.org
2020-07-02 10:39 ` markeggleston at gcc dot gnu.org
2020-07-02 15:31 ` kargl at gcc dot gnu.org [this message]
2020-07-02 15:53 ` jakub at gcc dot gnu.org
2020-07-02 16:41 ` sgk at troutmask dot apl.washington.edu
2020-07-02 17:10 ` schwab@linux-m68k.org
2020-07-02 17:15 ` sgk at troutmask dot apl.washington.edu
2020-07-02 17:24 ` schwab@linux-m68k.org
2020-07-02 18:41 ` sgk at troutmask dot apl.washington.edu
2021-11-03 20:19 ` egallager 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-52279-4-iRvhwA4i3M@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).