From: Mark Eggleston <mark.eggleston@codethink.co.uk>
To: David Edelsohn <dje.gcc@gmail.com>
Cc: GCC Patches <gcc-patches@gcc.gnu.org>,
Fortran List <fortran@gcc.gnu.org>,
msebor@gmail.com
Subject: Re: Fortran : Fortran translation issues PR52279
Date: Thu, 2 Jul 2020 11:16:44 +0100 [thread overview]
Message-ID: <ba2b2b08-d0cb-8d45-5b0f-433b817dfc8c@codethink.co.uk> (raw)
In-Reply-To: <9ef286ac-96c9-34e2-1cc8-41ebe09bad2e@codethink.co.uk>
I've committed the change from array to pointer. Does this fix your builds?
On 02/07/2020 08:18, Mark Eggleston wrote:
> On 01/07/2020 20:07, David Edelsohn wrote:
>> This patch breaks bootstrap.
>
> Apologies. I didn't see this when I built the compiler the with
> bootstrap on x86_64. I'll endevour to get it fixed as soon as possible.
>
> regards,
>
> Mark
>
>> It is not portable to use _( ... ) to initialize an array.
>>
>> In file included from
>> /nasfarm/edelsohn/src/src/gcc/fortran/gfortran.h:52,
>> from /nasfarm/edelsohn/src/src/gcc/fortran/check.c:32:
>> /nasfarm/edelsohn/src/src/gcc/fortran/check.c: In function 'bool
>> gfc_invalid_boz
>> (const char*, locus*)':
>> /nasfarm/edelsohn/src/src/gcc/intl.h:51:27: error: initializer fails
>> to determine size of 'hint'
>> 51 | # define _(msgid) gettext (msgid)
>> | ~~~~~~~~^~~~~~~
>> /nasfarm/edelsohn/src/src/gcc/fortran/check.c:70:23: note: in
>> expansion of macro
>> '_'
>> 70 | const char hint[] = _(" [see %<-fno-allow-invalid-boz%>]");
>> | ^
>> /nasfarm/edelsohn/src/src/gcc/intl.h:51:27: error: array must be
>> initialized with a brace-enclosed initializer
>>
--
https://www.codethink.co.uk/privacy.html
next prev parent reply other threads:[~2020-07-02 10:16 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-07-01 19:07 David Edelsohn
2020-07-02 7:18 ` Mark Eggleston
2020-07-02 10:16 ` Mark Eggleston [this message]
2020-07-02 12:17 ` David Edelsohn
2020-07-02 12:25 ` David Edelsohn
2020-07-02 12:56 ` Mark Eggleston
2020-07-02 13:06 ` Mark Eggleston
2020-07-02 13:38 ` David Edelsohn
2020-07-02 15:47 ` David Edelsohn
2020-07-03 13:22 ` David Edelsohn
-- strict thread matches above, loose matches on Subject: below --
2020-06-25 6:28 Mark Eggleston
2020-06-30 12:59 ` Mark Eggleston
2020-06-30 13:11 ` Thomas Koenig
2020-07-01 17:56 ` Martin Sebor
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=ba2b2b08-d0cb-8d45-5b0f-433b817dfc8c@codethink.co.uk \
--to=mark.eggleston@codethink.co.uk \
--cc=dje.gcc@gmail.com \
--cc=fortran@gcc.gnu.org \
--cc=gcc-patches@gcc.gnu.org \
--cc=msebor@gmail.com \
/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).