From: "Dominique d'Humières" <dominiq@lps.ens.fr>
To: Janne Blomqvist <blomqvist.janne@gmail.com>
Cc: Joseph Myers <joseph@codesourcery.com>,
gfortran <fortran@gcc.gnu.org>,
gcc-patches <gcc-patches@gcc.gnu.org>
Subject: Re: [PATCH] PR 78534, 83704 Large character lengths
Date: Sun, 21 Jan 2018 14:04:00 -0000 [thread overview]
Message-ID: <83AF33B2-5B86-46F2-9B89-545D241F4EEF@lps.ens.fr> (raw)
In-Reply-To: <CAO9iq9GpHOJEQBbhM1MK+nXt5DHAdV4+_yz_X0-RK64eK+Q=Uw@mail.gmail.com>
I use x86_64-apple-darwin17 and I run the test with -m32. Without the patch, a plain compilation leads to four errors and a timing
0.011u 0.008s 0:00.02 50.0% 0+0k 0+0io 13pf+0w
With the patch I get the four errors plus "Result of LEN overflows its kind » and a timing much slower
12.454u 21.185s 0:35.29 95.2% 0+0k 0+0io 955pf+0w
Dominique
> Le 21 janv. 2018 à 12:11, Janne Blomqvist <blomqvist.janne@gmail.com> a écrit :
>
> PING
>
> On Sun, Jan 14, 2018 at 2:33 PM, Janne Blomqvist
> <blomqvist.janne@gmail.com> wrote:
>> On Sun, Jan 14, 2018 at 12:45 PM, Janne Blomqvist
>> <blomqvist.janne@gmail.com> wrote:
>>> On Sat, Jan 13, 2018 at 7:35 PM, Dominique d'Humières
>>> <dominiq@tournesol.lps.ens.fr> wrote:
>>>> I have finally bootstrapped gfortran with the two patches applied and the spurious warnings with -Wall are now gone (limited testing), but I see a regression for gfortran.dg/string_1.f90 due to an additional error
>>>>
>>>> /opt/gcc/_clean/gcc/testsuite/gfortran.dg/string_1.f90:13:15:
>>>>
>>>> print *, len(s)
>>>> 1
>>>> Error: Result of LEN overflows its kind at (1)
>>>>
>>>> No idea why this was not emitted without the patch.
>>>
>>> Thanks for testing, I'll look into this. Was it on a 32 or 64-bit target?
>>
>> I can't recreate this on i686-pc-linux-gnu. What host/target are you
>> using exactly, is it part of the normal testsuite run or do you
>> compile it with some special options?
>>
>> In any case, that line isn't particularly relevant to what the
>> testcase is testing, so it could be removed completely, or by
>> specifying kind=8 to len().
>>
>>
>>
>>
>> --
>> Janne Blomqvist
>
>
>
> --
> Janne Blomqvist
next prev parent reply other threads:[~2018-01-21 14:04 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-01-10 13:35 Dominique d'Humières
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 [this message]
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=83AF33B2-5B86-46F2-9B89-545D241F4EEF@lps.ens.fr \
--to=dominiq@lps.ens.fr \
--cc=blomqvist.janne@gmail.com \
--cc=fortran@gcc.gnu.org \
--cc=gcc-patches@gcc.gnu.org \
--cc=joseph@codesourcery.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).