public inbox for fortran@gcc.gnu.org
 help / color / mirror / Atom feed
From: "Dominique d'Humières" <dominiq@tournesol.lps.ens.fr>
To: "jb at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
Cc: gfortran <fortran@gcc.gnu.org>, gcc-patches <gcc-patches@gcc.gnu.org>
Subject: Re: [PATCH] PR 78534, 83704 Large character lengths
Date: Wed, 10 Jan 2018 13:35:00 -0000	[thread overview]
Message-ID: <907C87F1-5F0F-4C47-972A-9C18589D2DAF@lps.ens.fr> (raw)

Hi Janne,

With this patch, bootstrap fails with

../../work/gcc/fortran/array.c: In function 'bool gfc_resolve_character_array_constructor(gfc_expr*)':
../../work/gcc/fortran/array.c:2062:36: error: unknown conversion type character 'l' in format [-Werror=format=]
     current_length, &p->expr->where);
                                    ^
../../work/gcc/fortran/array.c:2062:36: error: unknown conversion type character 'l' in format [-Werror=format=]
../../work/gcc/fortran/array.c:2062:36: error: format '%L' expects argument of type 'locus*', but argument 2 has type 'long long int' [-Werror=format]
../../work/gcc/fortran/array.c:2062:36: error: too many arguments for format [-Werror=format-extra-args]

Note that trying to only update I saw the same problem for data.c:179 and decl.c:1570/1580.

TIA

Dominique

             reply	other threads:[~2018-01-10 13:35 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-01-10 13:35 Dominique d'Humières [this message]
2018-01-12 19:57 ` Janne Blomqvist
2018-01-12 20:43   ` Joseph Myers
2018-01-13 17:35     ` Dominique d'Humières
2018-01-14 10:45       ` Janne Blomqvist
2018-01-14 10:55         ` Thomas Koenig
2018-01-14 12:33         ` Janne Blomqvist
2018-01-21 11:11           ` Janne Blomqvist
2018-01-21 14:04             ` Dominique d'Humières
2018-01-21 18:30             ` Steve Kargl
2018-01-21 19:49               ` Janne Blomqvist
2018-01-21 19:58                 ` Steve Kargl
  -- strict thread matches above, loose matches on Subject: below --
2018-01-09 12:07 Janne Blomqvist

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=907C87F1-5F0F-4C47-972A-9C18589D2DAF@lps.ens.fr \
    --to=dominiq@tournesol.lps.ens.fr \
    --cc=fortran@gcc.gnu.org \
    --cc=gcc-bugzilla@gcc.gnu.org \
    --cc=gcc-patches@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).