[Bug fortran/67429] New: [5/6 Regression] Missing part of error messages.

[Bug fortran/67429] New: [5/6 Regression] Missing part of error messages.

[dominiq at lps dot ens.fr]

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=67429

            Bug ID: 67429
           Summary: [5/6 Regression] Missing part of error messages.
           Product: gcc
           Version: 6.0
            Status: UNCONFIRMED
          Severity: normal
          Priority: P3
         Component: fortran
          Assignee: unassigned at gcc dot gnu.org
          Reporter: dominiq at lps dot ens.fr
                CC: burnus@net-b.de, manu at gcc dot gnu.org
  Target Milestone: ---

When compiling the test in pr65045 with r218570 I get the errors

pr65045.f90:3.6:

 if (i>7.7) then
      1
Error: Symbol at (1) is not appropriate for an expression
pr65045.f90:5.7:

   else
       1
Error: Unexpected ELSE statement at (1)
pr65045.f90:6.6:

     i = 2.2
      1
Error: 'i' at (1) is not a variable
pr65045.f90:7.6:

   end if
      1
Error: Expecting END BLOCK statement at (1)
f951: internal compiler error: Segmentation fault: 11

f951: internal compiler error: Abort trap: 6
gfortran: internal compiler error: Abort trap: 6 (program f951)
Abort

With revision r218658, the errors are

pr65045.f90:3:6: Error: Symbol at (1) is not appropriate for an expression
pr65045.f90:5:7:

    else
       1
Error: Unexpected ELSE statement at (1)
pr65045.f90:6:6: Error: 'i' at (1) is not a variable
pr65045.f90:7:6:

    end if
      1
Error: Expecting END BLOCK statement at (1)
(null):0: confused by earlier errors, bailing out

Likely r218619 or r218627.

This may explain pr67174.

[Bug fortran/67429] [5/6 Regression] Missing part of error messages.

[kargl at gcc dot gnu.org]

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=67429

kargl at gcc dot gnu.org changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |kargl at gcc dot gnu.org

--- Comment #1 from kargl at gcc dot gnu.org ---
(In reply to Dominique d'Humieres from comment #0)
> When compiling the test in pr65045 with r218570 I get the errors
> 

So, why isn't this a duplicate of PR65045?

[Bug fortran/67429] [5/6 Regression] Missing part of error messages.

[dominiq at lps dot ens.fr]

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=67429

--- Comment #2 from Dominique d'Humieres <dominiq at lps dot ens.fr> ---
> So, why isn't this a duplicate of PR65045?

Because PR65045 is about an ICE and this PR is about missing text in the error
messages.

[Bug fortran/67429] [5/6 Regression] Missing part of error messages.

[sgk at troutmask dot apl.washington.edu]

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=67429

--- Comment #3 from Steve Kargl <sgk at troutmask dot apl.washington.edu> ---
On Tue, Sep 01, 2015 at 08:05:33PM +0000, dominiq at lps dot ens.fr wrote:
> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=67429
> 
> --- Comment #2 from Dominique d'Humieres <dominiq at lps dot ens.fr> ---
> > So, why isn't this a duplicate of PR65045?
> 
> Because PR65045 is about an ICE and this PR is about missing text in the error
> messages.
> 

It's the same piece of code causing the problem.  One
needs to go to PR65045 to get the code, so this PR
is superfluous.  When the ICE is fixed, then
error message should be addressed.

[Bug fortran/67429] [5/6 Regression] Missing part of error messages.

[dominiq at lps dot ens.fr]

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=67429

--- Comment #4 from Dominique d'Humieres <dominiq at lps dot ens.fr> ---
> It's the same piece of code causing the problem.  One
> needs to go to PR65045 to get the code, so this PR
> is superfluous.  When the ICE is fixed, then
> error message should be addressed.

The piece of code is used as an example exhibiting a different problem than
PR65045.
Please read comment 0.

[Bug fortran/67429] [5/6 Regression] Missing part of error messages.

[sgk at troutmask dot apl.washington.edu]

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=67429

--- Comment #5 from Steve Kargl <sgk at troutmask dot apl.washington.edu> ---
>
> Please read comment 0.
> 

I read comment #0.

THERE IS NO CODE THERE.

THERE IS NO CODE ATTACHED TO THIS PR.

One needs to go to PR65045 to get the code
that is causing the error message.  Ergo,
this is a duplicate of PR65045.

When PR65045 is fixed.  The issue with the
error message should be addressed then.

[Bug fortran/67429] [5/6 Regression] Missing part of error messages.

[pault at gcc dot gnu.org]

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=67429

Paul Thomas <pault at gcc dot gnu.org> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |pault at gcc dot gnu.org

--- Comment #6 from Paul Thomas <pault at gcc dot gnu.org> ---
Created attachment 36283
  --> https://gcc.gnu.org/bugzilla/attachment.cgi?id=36283&action=edit
Patch for PR65045 that displays the problem

[Bug fortran/67429] [5/6 Regression] Missing part of error messages.

[pault at gcc dot gnu.org]

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=67429

--- Comment #7 from Paul Thomas <pault at gcc dot gnu.org> ---
(In reply to Steve Kargl from comment #5)
> >
> > Please read comment 0.
> > 
> 
> I read comment #0.
> 
> THERE IS NO CODE THERE.
> 
> THERE IS NO CODE ATTACHED TO THIS PR.
> 
> One needs to go to PR65045 to get the code
> that is causing the error message.  Ergo,
> this is a duplicate of PR65045.
> 
> When PR65045 is fixed.  The issue with the
> error message should be addressed then.

Steve,

This is a problem that has surfaced with the change to the gcc error handling.
Rainer Orth has encountered it on Solaris and it caused me to hold back on my
patch for pointer function assignment.

The patch for PR65045 is the simplest manifestation that I have found. I am
very grateful to Dominique for posting this PR because the problem has been
driving me crazy. I assumed that it was my patches that were wrong. However,
Dominique proved by going through different revisions that the December 2014
patches to error.c are the culprits.

Go easy on us both - it's getting a bit late here :-)

Cheers

Paul

[Bug fortran/67429] [5/6 Regression] Missing part of error messages.

[dominiq at lps dot ens.fr]

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=67429

Dominique d'Humieres <dominiq at lps dot ens.fr> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|UNCONFIRMED                 |NEW
   Last reconfirmed|                            |2015-09-01
     Ever confirmed|0                           |1

--- Comment #8 from Dominique d'Humieres <dominiq at lps dot ens.fr> ---
> Created attachment 36283 [details]
> Patch for PR65045 that displays the problem

Paul,

Your patch for gcc/fortran/decl.c does not apply on trunk:

 if (state == COMP_BLOCK)

is now

 while (state == COMP_BLOCK)

[Bug fortran/67429] [5/6 Regression] Missing part of error messages.

[manu at gcc dot gnu.org]

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=67429

--- Comment #9 from Manuel López-Ibáñez <manu at gcc dot gnu.org> ---
Even with the original patch applied to r227391, I cannot reproduce the error
that you get. On x86_64-linux-gnu, I get:

Starting program: /home/manuel/test1/226953M/build/gcc/f951
~/test1/src/gcc/testsuite/gfortran.dg/pr65045.f90
/home/manuel/test1/src/gcc/testsuite/gfortran.dg/pr65045.f90:7:6: Error: Symbol
‘i’ at (1) is not appropriate for an expression
/home/manuel/test1/src/gcc/testsuite/gfortran.dg/pr65045.f90:9:59:

    else          ! { dg-error "Unexpected ELSE statement" }
                                                           1
Error: Unexpected ELSE statement at (1)
/home/manuel/test1/src/gcc/testsuite/gfortran.dg/pr65045.f90:10:6: Error: ‘i’
at (1) is not a variable
/home/manuel/test1/src/gcc/testsuite/gfortran.dg/pr65045.f90:11:6:

    end if        ! { dg-error "Expecting END BLOCK statement" }
      1
Error: Expecting END BLOCK statement at (1)
/home/manuel/test1/src/gcc/testsuite/gfortran.dg/pr65045.f90:13:8:

 print*,i         ! { dg-error "not appropriate for an expression" }
        1
Error: Symbol ‘i’ at (1) is not appropriate for an expression


However, there is a bug indeed. The first caret line is not printed because
there was a previous buffered error at the same location that later got
cleared. However, clearing it does not reset context->last_location, which is
checked in gfc_diagnostic_starter.

This patch seems to fix it:

Index: error.c
===================================================================
--- error.c     (revision 227391)
+++ error.c     (working copy)
@@ -755,10 +755,13 @@ gfc_clear_pp_buffer (output_buffer *this
   pretty_printer *pp = global_dc->printer;
   output_buffer *tmp_buffer = pp->buffer;
   pp->buffer = this_buffer;
   pp_clear_output_area (pp);
   pp->buffer = tmp_buffer;
+  /* We need to reset last_location, otherwise we may skip caret lines
+     when we actually give a diagnostic.  */
+  global_dc->last_location = UNKNOWN_LOCATION;
 }



However, it is not a very nice solution. It may happen that we give an error at
location X, then we buffer some errors, then we clear them, so we reset last
location to UNKNOWN, then we give an error at location X and we will get a
duplicated caret line. Thus, it would be better if last_location was only
updated when we actually flush the output text. However, that would require
some deeper changes, probably in diagnostic.c and in fortran/error.c to handle
both buffered and not buffered output_buffers. On the other hand, I'm not sure
the previous Fortran diagnostic machinery cared about duplicated caret lines,
thus perhaps the above is enough.

BTW, you should use %qs instead of '%s' in order to get quoting localized to
the user's language and color highlighting.
>From gcc-bugs-return-496130-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Wed Sep 02 00:41:43 2015
Return-Path: <gcc-bugs-return-496130-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 99798 invoked by alias); 2 Sep 2015 00:41:43 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 99707 invoked by uid 48); 2 Sep 2015 00:41:39 -0000
From: "manu at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug fortran/67174] [6 regression] gfortran.dg/do_iterator.f90 FAILs
Date: Wed, 02 Sep 2015 00:41:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: fortran
X-Bugzilla-Version: 6.0
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: manu at gcc dot gnu.org
X-Bugzilla-Status: RESOLVED
X-Bugzilla-Resolution: INVALID
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: 6.0
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: cc
Message-ID: <bug-67174-4-R3nR2QXtkC@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-67174-4@http.gcc.gnu.org/bugzilla/>
References: <bug-67174-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2015-09/txt/msg00108.txt.bz2
Content-length: 1472

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=67174

Manuel López-Ibáñez <manu at gcc dot gnu.org> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |manu at gcc dot gnu.org

--- Comment #5 from Manuel López-Ibáñez <manu at gcc dot gnu.org> ---
(In reply to paul.richard.thomas@gmail.com from comment #4)
> reworked to use the gcc error reporting mechanisms. There is now a
> flag, which determines whether or not the line where the error occurs
> is displayed or not. I suspect that something is causing this flag to

https://gcc.gnu.org/onlinedocs/gcc/Diagnostic-Message-Formatting-Options.html#Diagnostic-Message-Formatting-Options

The flag is -fdiagnostics-show-caret. The testsuite uses
-fno-diagnostics-show-caret, since we actually cannot test the caret line (the
source line with the '(1)' or '(2)' or '^' symbol below) and the info given by
-fno-diagnostics-show-caret is enough to test precise locations. The Fortran FE
testsuite uses several complicated regex to remove all possible forms of the
caret line and keep only the location information and the diagnostic text, but
I think this should not be necessary anymore since everything was converted to
the common machinery and the output with -fno-diagnostics-show-caret is already
in the desired form for the testsuite.
>From gcc-bugs-return-496131-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Wed Sep 02 00:57:08 2015
Return-Path: <gcc-bugs-return-496131-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 105997 invoked by alias); 2 Sep 2015 00:57:07 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 105936 invoked by uid 48); 2 Sep 2015 00:57:04 -0000
From: "manu at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug fortran/67429] [5/6 Regression] Missing part of error messages.
Date: Wed, 02 Sep 2015 00:57:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: fortran
X-Bugzilla-Version: 6.0
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: manu at gcc dot gnu.org
X-Bugzilla-Status: NEW
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-67429-4-Ph1hPAxsoY@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-67429-4@http.gcc.gnu.org/bugzilla/>
References: <bug-67429-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2015-09/txt/msg00109.txt.bz2
Content-length: 1176

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=67429

--- Comment #10 from Manuel López-Ibáñez <manu at gcc dot gnu.org> ---
(In reply to Paul Thomas from comment #7)
> The patch for PR65045 is the simplest manifestation that I have found. I am
> very grateful to Dominique for posting this PR because the problem has been
> driving me crazy. I assumed that it was my patches that were wrong. However,
> Dominique proved by going through different revisions that the December 2014
> patches to error.c are the culprits.

(In reply to Dominique d'Humieres from comment #0)

> Error: Expecting END BLOCK statement at (1)
> (null):0: confused by earlier errors, bailing out

Even if *I* cannot reproduce this, such an error should be easy to debug: Just
put a break in diagnostic_report_diagnostic on the line that gives this message
and go up to find out what triggered this code to run. My guess is that you are
somehow triggering an ICE while reporting an ICE. It would be interesting to
understand where that strange location comes from (I guess it is
UNKNOWN_LOCATION?). And also to harden that code to not try to print a null
s.file pointer!
>From gcc-bugs-return-496132-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Wed Sep 02 02:46:05 2015
Return-Path: <gcc-bugs-return-496132-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 57403 invoked by alias); 2 Sep 2015 02:46:05 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 57366 invoked by uid 48); 2 Sep 2015 02:46:00 -0000
From: "peter at cordes dot ca" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug rtl-optimization/42497] Generate conditional tail calls .
Date: Wed, 02 Sep 2015 02:46:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: rtl-optimization
X-Bugzilla-Version: 4.5.0
X-Bugzilla-Keywords: missed-optimization
X-Bugzilla-Severity: enhancement
X-Bugzilla-Who: peter at cordes dot ca
X-Bugzilla-Status: NEW
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: cc
Message-ID: <bug-42497-4-rXjX0rt3Ln@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-42497-4@http.gcc.gnu.org/bugzilla/>
References: <bug-42497-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: 7bit
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2015-09/txt/msg00110.txt.bz2
Content-length: 1325

https://gcc.gnu.org/bugzilla/show_bug.cgi?idB497

Peter Cordes <peter at cordes dot ca> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |peter at cordes dot ca

--- Comment #3 from Peter Cordes <peter at cordes dot ca> ---
This bug is still present with gcc 5.2 -O3 (which does include
-foptimize-sibling-calls).


void fire_special_event(void);
void conditional_call(int cond) {  if(cond) fire_special_event();   }

 The above code compiles to (x86-64 gcc 5.2 -O3)

        testl   %edi, %edi
        jne     .L4
        rep ret
 .L4:
        jmp     fire_special_event


  This sequence would be better:
        testl   %edi, %edi
        jne     fire_special_event
        ret

godbolt link: https://goo.gl/0K6EZx
Later functions in that listing are related to
http://stackoverflow.com/questions/97987/advantage-of-switch-over-if-else-statement


 Is there a linker limitation on relocations for conditional-branch targets
that aren't part of the current compilation unit?  neither clang 3.7 nor icc 13
do any better than gcc.  It seems to work for me when modifying the asm by hand
to          jnz     _Z18fire_special_eventv, and linking to a
separately-compiled definition.

[Bug fortran/67429] [5/6 Regression] Missing part of error messages.

[dominiq at lps dot ens.fr]

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=67429

--- Comment #11 from Dominique d'Humieres <dominiq at lps dot ens.fr> ---
(In reply to Manuel López-Ibáñez  from comment #10)

> > Error: Expecting END BLOCK statement at (1)
> > (null):0: confused by earlier errors, bailing out
>
>
> Even if *I* cannot reproduce this, such an error should be easy to debug:
> Just put a break in diagnostic_report_diagnostic on the line that gives
> this message and go up to find out what triggered this code to run.
> My guess is that you are somehow triggering an ICE while reporting an ICE.
> It would be interesting to understand where that strange location comes
> from (I guess it is UNKNOWN_LOCATION?). And also to harden that code to not
> try to print a null s.file pointer!

Sorry for the confusion I sometime get this kind of error instead of the usual
ICE when using compilers configured with '--enable-checking=release'.
>From gcc-bugs-return-496152-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Wed Sep 02 09:04:31 2015
Return-Path: <gcc-bugs-return-496152-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 35518 invoked by alias); 2 Sep 2015 09:04:31 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 35471 invoked by uid 48); 2 Sep 2015 09:04:27 -0000
From: "xuejuncao at gmail dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c/67433] ?: expression returns unexpected value when condition is a bool variable which memory is not true/false
Date: Wed, 02 Sep 2015 09:04:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: c
X-Bugzilla-Version: 6.0
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: xuejuncao at gmail dot com
X-Bugzilla-Status: RESOLVED
X-Bugzilla-Resolution: INVALID
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-67433-4-VbD8ilbHXY@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-67433-4@http.gcc.gnu.org/bugzilla/>
References: <bug-67433-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: 7bit
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2015-09/txt/msg00130.txt.bz2
Content-length: 693

https://gcc.gnu.org/bugzilla/show_bug.cgi?idg433

--- Comment #8 from xuejuncao <xuejuncao at gmail dot com> ---
thanks, i get the below result with -fsanitize=undefined

boolmagic.c:12:16: runtime error: load of value 255, which is not a valid value
for type '_Bool'
boolmagic.c:13:15: runtime error: load of value 255, which is not a valid value
for type '_Bool'
boolmagic.c:14:15: runtime error: load of value 255, which is not a valid value
for type '_Bool'
b = 1, i = 1, j = 1

but, can i say the "-fsanitize=undefined" will _corrects_ the undefined
behaviour?

or replace the code by if/else, which works fine (lucky?)

    int i; // = (u.b ? 1 : 0);
    if (u.b) i = 1; else i = 0;

[Bug fortran/67429] [5/6 Regression] Missing part of error messages.

[dominiq at lps dot ens.fr]

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=67429

--- Comment #12 from Dominique d'Humieres <dominiq at lps dot ens.fr> ---
> > Created attachment 36283 [details]
> > Patch for PR65045 that displays the problem
>
> Paul,
>
> Your patch for gcc/fortran/decl.c does not apply on trunk:
>
>  if (state == COMP_BLOCK)
>
> is now
>
>  while (state == COMP_BLOCK)

With the adjusted patch (IF replaced with WHILE) the ICE in PR65045 is gone and
gfortran retest cleanly, even if the error for the new test is

/opt/gcc/p_work/gcc/testsuite/gfortran.dg/pr65045.f90:7:6: Error: Symbol 'i' at
(1) is not appropriate for an expression
/opt/gcc/p_work/gcc/testsuite/gfortran.dg/pr65045.f90:9:59:

    else          ! { dg-error "Unexpected ELSE statement" }
                                                           1
Error: Unexpected ELSE statement at (1)
/opt/gcc/p_work/gcc/testsuite/gfortran.dg/pr65045.f90:10:6: Error: 'i' at (1)
is not a variable
/opt/gcc/p_work/gcc/testsuite/gfortran.dg/pr65045.f90:11:6:

    end if        ! { dg-error "Expecting END BLOCK statement" }
      1
Error: Expecting END BLOCK statement at (1)
/opt/gcc/p_work/gcc/testsuite/gfortran.dg/pr65045.f90:13:8:

 print*,i         ! { dg-error "not appropriate for an expression" }
        1
Error: Symbol 'i' at (1) is not appropriate for an expression

[Bug fortran/67429] [5/6 Regression] Missing part of error messages.

[rguenth at gcc dot gnu.org]

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=67429

Richard Biener <rguenth at gcc dot gnu.org> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
   Target Milestone|---                         |5.3

[Bug fortran/67429] [5/6 Regression] Missing part of error messages.

[dominiq at lps dot ens.fr]

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=67429

--- Comment #13 from Dominique d'Humieres <dominiq at lps dot ens.fr> ---
The patch in comment 9 restores the old (correct?) behavior without regression.

[Bug fortran/67429] [5/6 Regression] Missing part of error messages.

[pault at gcc dot gnu.org]

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=67429

--- Comment #14 from Paul Thomas <pault at gcc dot gnu.org> ---
(In reply to Dominique d'Humieres from comment #13)
> The patch in comment 9 restores the old (correct?) behavior without
> regression.

Indeed and it gets rid of the problems that I have been encountering.

Manuel,

Do you want to commit or would you like me to do it?

Cheers

Paul

[Bug fortran/67429] [5/6 Regression] Missing part of error messages.

[manu at gcc dot gnu.org]

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=67429

--- Comment #15 from Manuel López-Ibáñez <manu at gcc dot gnu.org> ---
(In reply to Paul Thomas from comment #14)
> Do you want to commit or would you like me to do it?

Please do, I'll have little time for gcc in the next weeks. Thanks.
>From gcc-bugs-return-496227-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Wed Sep 02 18:52:53 2015
Return-Path: <gcc-bugs-return-496227-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 43332 invoked by alias); 2 Sep 2015 18:52:53 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 43286 invoked by uid 48); 2 Sep 2015 18:52:48 -0000
From: "rmansfield at qnx dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug target/67439] New: ICE: unrecognizable insn compiling arm-fp16 testcases with -march=armv7-a and -mrestrict-it
Date: Wed, 02 Sep 2015 18:52:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: new
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: target
X-Bugzilla-Version: 6.0
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: rmansfield at qnx dot com
X-Bugzilla-Status: UNCONFIRMED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: bug_id short_desc product version bug_status bug_severity priority component assigned_to reporter target_milestone cf_gcctarget
Message-ID: <bug-67439-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: 7bit
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2015-09/txt/msg00205.txt.bz2
Content-length: 14097

https://gcc.gnu.org/bugzilla/show_bug.cgi?idg439

            Bug ID: 67439
           Summary: ICE: unrecognizable insn compiling arm-fp16 testcases
                    with -march=armv7-a and -mrestrict-it
           Product: gcc
           Version: 6.0
            Status: UNCONFIRMED
          Severity: normal
          Priority: P3
         Component: target
          Assignee: unassigned at gcc dot gnu.org
          Reporter: rmansfield at qnx dot com
  Target Milestone: ---
            Target: arm-unknown-linux-gnueabi

$ ./xgcc -v
Using built-in specs.
COLLECT_GCC=./xgcc
Target: arm-unknown-linux-gnueabi
Configured with: ../configure --target=arm-unknown-linux-gnueabi
--prefix=/home/rmansfield/x-tools/arm-unknown-linux-gnueabi
--with-sysroot=/home/rmansfield/x-tools/arm-unknown-linux-gnueabi/arm-unknown-linux-gnueabi//sys-root
--disable-multilib
--with-local-prefix=/home/rmansfield/x-tools/arm-unknown-linux-gnueabi/arm-unknown-linux-gnueabi/sys-root
--disable-nls --enable-threads=posix --enable-symvers=gnu --enable-c99
--enable-long-long --enable-target-optspace
target_alias=arm-unknown-linux-gnueabi --enable-languages=c++
--disable-libmudflap --disable-libssp --enable-checking
Thread model: posix
gcc version 6.0.0 20150902 (experimental) [trunk revision 227416] (GCC)

$ ./xgcc -B. ../../gcc/testsuite/gcc.dg/torture/arm-fp16-compile-assign.c  -O0
-mfp16-format=ieee  -S    -o arm-fp16-compile-assign.s   -O2 -march=armv7-a
-mrestrict-it
rmansfield@BB1543999644:~/gnu/gcc/trunk/arm-eabi/gcc$ ./xgcc -B.
../../gcc/testsuite/gcc.dg/torture/arm-fp16-compile-assign.c  -O0
-mfp16-format=ieee  -S    -o arm-fp16-compile-assign.s   -O2 -mthumb
-march=armv7-a -mrestrict-it
../../gcc/testsuite/gcc.dg/torture/arm-fp16-compile-assign.c: In function 'f':
../../gcc/testsuite/gcc.dg/torture/arm-fp16-compile-assign.c:25:1: error:
unrecognizable insn:
 }
 ^
(insn 7 6 8 2 (set (reg:HF 118)
        (const_double:HF 1.0e+0 [0x0.8p+1]))
../../gcc/testsuite/gcc.dg/torture/arm-fp16-compile-assign.c:17 -1
     (nil))
../../gcc/testsuite/gcc.dg/torture/arm-fp16-compile-assign.c:25:1: internal
compiler error: in extract_insn, at recog.c:2297
0x9e8ec5 _fatal_insn(char const*, rtx_def const*, char const*, int, char
const*)
        ../../gcc/rtl-error.c:109
0x9e8ef9 _fatal_insn_not_found(rtx_def const*, char const*, int, char const*)
        ../../gcc/rtl-error.c:117
0x9baaa7 extract_insn(rtx_insn*)
        ../../gcc/recog.c:2297
0x7e7e52 instantiate_virtual_regs_in_insn
        ../../gcc/function.c:1589
0x7e7e52 instantiate_virtual_regs
        ../../gcc/function.c:1957
0x7e7e52 execute
        ../../gcc/function.c:2006
Please submit a full bug report,
with preprocessed source if appropriate.
Please include the complete backtrace with any bug report.
See <http://gcc.gnu.org/bugs.html> for instructions.

FAIL: gcc.dg/torture/arm-fp16-compile-assign.c   -O0  (internal compiler error)
FAIL: gcc.dg/torture/arm-fp16-compile-assign.c   -O0  (test for excess errors)
FAIL: gcc.dg/torture/arm-fp16-compile-assign.c   -O1  (internal compiler error)
FAIL: gcc.dg/torture/arm-fp16-compile-assign.c   -O1  (test for excess errors)
FAIL: gcc.dg/torture/arm-fp16-compile-assign.c   -O2  (internal compiler error)
FAIL: gcc.dg/torture/arm-fp16-compile-assign.c   -O2  (test for excess errors)
FAIL: gcc.dg/torture/arm-fp16-compile-assign.c   -O3 -fomit-frame-pointer
(internal compiler error)
FAIL: gcc.dg/torture/arm-fp16-compile-assign.c   -O3 -fomit-frame-pointer
(test for excess errors)
FAIL: gcc.dg/torture/arm-fp16-compile-assign.c   -O3 -g  (internal compiler
error)
FAIL: gcc.dg/torture/arm-fp16-compile-assign.c   -O3 -g  (test for excess
errors)
FAIL: gcc.dg/torture/arm-fp16-compile-assign.c   -Os  (internal compiler error)
FAIL: gcc.dg/torture/arm-fp16-compile-assign.c   -Os  (test for excess errors)
FAIL: gcc.dg/torture/arm-fp16-compile-assign.c   -O2 -flto
-fno-use-linker-plugin -flto-partition=none  (internal compiler error)
FAIL: gcc.dg/torture/arm-fp16-compile-assign.c   -O2 -flto
-fno-use-linker-plugin -flto-partition=none  (test for excess errors)
FAIL: gcc.dg/torture/arm-fp16-compile-assign.c   -O2 -flto -fuse-linker-plugin
-fno-fat-lto-objects  (internal compiler error)
FAIL: gcc.dg/torture/arm-fp16-compile-assign.c   -O2 -flto -fuse-linker-plugin
-fno-fat-lto-objects  (test for excess errors)
FAIL: gcc.dg/torture/arm-fp16-compile-convert.c   -O0  (internal compiler
error)
FAIL: gcc.dg/torture/arm-fp16-compile-convert.c   -O0  (test for excess errors)
FAIL: gcc.dg/torture/arm-fp16-compile-convert.c   -O1  (internal compiler
error)
FAIL: gcc.dg/torture/arm-fp16-compile-convert.c   -O1  (test for excess errors)
FAIL: gcc.dg/torture/arm-fp16-compile-convert.c   -O2  (internal compiler
error)
FAIL: gcc.dg/torture/arm-fp16-compile-convert.c   -O2  (test for excess errors)
FAIL: gcc.dg/torture/arm-fp16-compile-convert.c   -O3 -fomit-frame-pointer
(internal compiler error)
FAIL: gcc.dg/torture/arm-fp16-compile-convert.c   -O3 -fomit-frame-pointer
(test for excess errors)
FAIL: gcc.dg/torture/arm-fp16-compile-convert.c   -O3 -g  (internal compiler
error)
FAIL: gcc.dg/torture/arm-fp16-compile-convert.c   -O3 -g  (test for excess
errors)
FAIL: gcc.dg/torture/arm-fp16-compile-convert.c   -Os  (internal compiler
error)
FAIL: gcc.dg/torture/arm-fp16-compile-convert.c   -Os  (test for excess errors)
FAIL: gcc.dg/torture/arm-fp16-compile-convert.c   -O2 -flto
-fno-use-linker-plugin -flto-partition=none  (internal compiler error)
FAIL: gcc.dg/torture/arm-fp16-compile-convert.c   -O2 -flto
-fno-use-linker-plugin -flto-partition=none  (test for excess errors)
FAIL: gcc.dg/torture/arm-fp16-compile-convert.c   -O2 -flto -fuse-linker-plugin
-fno-fat-lto-objects  (internal compiler error)
FAIL: gcc.dg/torture/arm-fp16-compile-convert.c   -O2 -flto -fuse-linker-plugin
-fno-fat-lto-objects  (test for excess errors)
FAIL: gcc.dg/torture/arm-fp16-ops-1.c   -O0  (internal compiler error)
FAIL: gcc.dg/torture/arm-fp16-ops-1.c   -O0  (test for excess errors)
FAIL: gcc.dg/torture/arm-fp16-ops-1.c   -O1  (internal compiler error)
FAIL: gcc.dg/torture/arm-fp16-ops-1.c   -O1  (test for excess errors)
FAIL: gcc.dg/torture/arm-fp16-ops-1.c   -O2  (internal compiler error)
FAIL: gcc.dg/torture/arm-fp16-ops-1.c   -O2  (test for excess errors)
FAIL: gcc.dg/torture/arm-fp16-ops-1.c   -O3 -fomit-frame-pointer  (internal
compiler error)
FAIL: gcc.dg/torture/arm-fp16-ops-1.c   -O3 -fomit-frame-pointer  (test for
excess errors)
FAIL: gcc.dg/torture/arm-fp16-ops-1.c   -O3 -g  (internal compiler error)
FAIL: gcc.dg/torture/arm-fp16-ops-1.c   -O3 -g  (test for excess errors)
FAIL: gcc.dg/torture/arm-fp16-ops-1.c   -Os  (internal compiler error)
FAIL: gcc.dg/torture/arm-fp16-ops-1.c   -Os  (test for excess errors)
FAIL: gcc.dg/torture/arm-fp16-ops-1.c   -O2 -flto -fno-use-linker-plugin
-flto-partition=none  (internal compiler error)
FAIL: gcc.dg/torture/arm-fp16-ops-1.c   -O2 -flto -fno-use-linker-plugin
-flto-partition=none  (test for excess errors)
FAIL: gcc.dg/torture/arm-fp16-ops-1.c   -O2 -flto -fuse-linker-plugin
-fno-fat-lto-objects  (internal compiler error)
FAIL: gcc.dg/torture/arm-fp16-ops-1.c   -O2 -flto -fuse-linker-plugin
-fno-fat-lto-objects  (test for excess errors)
FAIL: gcc.dg/torture/arm-fp16-ops-2.c   -O0  (internal compiler error)
FAIL: gcc.dg/torture/arm-fp16-ops-2.c   -O0  (test for excess errors)
FAIL: gcc.dg/torture/arm-fp16-ops-2.c   -O1  (internal compiler error)
FAIL: gcc.dg/torture/arm-fp16-ops-2.c   -O1  (test for excess errors)
FAIL: gcc.dg/torture/arm-fp16-ops-2.c   -O2  (internal compiler error)
FAIL: gcc.dg/torture/arm-fp16-ops-2.c   -O2  (test for excess errors)
FAIL: gcc.dg/torture/arm-fp16-ops-2.c   -O3 -fomit-frame-pointer  (internal
compiler error)
FAIL: gcc.dg/torture/arm-fp16-ops-2.c   -O3 -fomit-frame-pointer  (test for
excess errors)
FAIL: gcc.dg/torture/arm-fp16-ops-2.c   -O3 -g  (internal compiler error)
FAIL: gcc.dg/torture/arm-fp16-ops-2.c   -O3 -g  (test for excess errors)
FAIL: gcc.dg/torture/arm-fp16-ops-2.c   -Os  (internal compiler error)
FAIL: gcc.dg/torture/arm-fp16-ops-2.c   -Os  (test for excess errors)
FAIL: gcc.dg/torture/arm-fp16-ops-2.c   -O2 -flto -fno-use-linker-plugin
-flto-partition=none  (internal compiler error)
FAIL: gcc.dg/torture/arm-fp16-ops-2.c   -O2 -flto -fno-use-linker-plugin
-flto-partition=none  (test for excess errors)
FAIL: gcc.dg/torture/arm-fp16-ops-2.c   -O2 -flto -fuse-linker-plugin
-fno-fat-lto-objects  (internal compiler error)
FAIL: gcc.dg/torture/arm-fp16-ops-2.c   -O2 -flto -fuse-linker-plugin
-fno-fat-lto-objects  (test for excess errors)
FAIL: gcc.dg/torture/arm-fp16-ops-3.c   -O0  (internal compiler error)
FAIL: gcc.dg/torture/arm-fp16-ops-3.c   -O0  (test for excess errors)
FAIL: gcc.dg/torture/arm-fp16-ops-3.c   -O1  (internal compiler error)
FAIL: gcc.dg/torture/arm-fp16-ops-3.c   -O1  (test for excess errors)
FAIL: gcc.dg/torture/arm-fp16-ops-3.c   -O2  (internal compiler error)
FAIL: gcc.dg/torture/arm-fp16-ops-3.c   -O2  (test for excess errors)
FAIL: gcc.dg/torture/arm-fp16-ops-3.c   -O3 -fomit-frame-pointer  (internal
compiler error)
FAIL: gcc.dg/torture/arm-fp16-ops-3.c   -O3 -fomit-frame-pointer  (test for
excess errors)
FAIL: gcc.dg/torture/arm-fp16-ops-3.c   -O3 -g  (internal compiler error)
FAIL: gcc.dg/torture/arm-fp16-ops-3.c   -O3 -g  (test for excess errors)
FAIL: gcc.dg/torture/arm-fp16-ops-3.c   -Os  (internal compiler error)
FAIL: gcc.dg/torture/arm-fp16-ops-3.c   -Os  (test for excess errors)
FAIL: gcc.dg/torture/arm-fp16-ops-3.c   -O2 -flto -fno-use-linker-plugin
-flto-partition=none  (internal compiler error)
FAIL: gcc.dg/torture/arm-fp16-ops-3.c   -O2 -flto -fno-use-linker-plugin
-flto-partition=none  (test for excess errors)
FAIL: gcc.dg/torture/arm-fp16-ops-3.c   -O2 -flto -fuse-linker-plugin
-fno-fat-lto-objects  (internal compiler error)
FAIL: gcc.dg/torture/arm-fp16-ops-3.c   -O2 -flto -fuse-linker-plugin
-fno-fat-lto-objects  (test for excess errors)
FAIL: gcc.dg/torture/arm-fp16-ops-4.c   -O0  (internal compiler error)
FAIL: gcc.dg/torture/arm-fp16-ops-4.c   -O0  (test for excess errors)
FAIL: gcc.dg/torture/arm-fp16-ops-4.c   -O1  (internal compiler error)
FAIL: gcc.dg/torture/arm-fp16-ops-4.c   -O1  (test for excess errors)
FAIL: gcc.dg/torture/arm-fp16-ops-4.c   -O2  (internal compiler error)
FAIL: gcc.dg/torture/arm-fp16-ops-4.c   -O2  (test for excess errors)
FAIL: gcc.dg/torture/arm-fp16-ops-4.c   -O3 -fomit-frame-pointer  (internal
compiler error)
FAIL: gcc.dg/torture/arm-fp16-ops-4.c   -O3 -fomit-frame-pointer  (test for
excess errors)
FAIL: gcc.dg/torture/arm-fp16-ops-4.c   -O3 -g  (internal compiler error)
FAIL: gcc.dg/torture/arm-fp16-ops-4.c   -O3 -g  (test for excess errors)
FAIL: gcc.dg/torture/arm-fp16-ops-4.c   -Os  (internal compiler error)
FAIL: gcc.dg/torture/arm-fp16-ops-4.c   -Os  (test for excess errors)
FAIL: gcc.dg/torture/arm-fp16-ops-4.c   -O2 -flto -fno-use-linker-plugin
-flto-partition=none  (internal compiler error)
FAIL: gcc.dg/torture/arm-fp16-ops-4.c   -O2 -flto -fno-use-linker-plugin
-flto-partition=none  (test for excess errors)
FAIL: gcc.dg/torture/arm-fp16-ops-4.c   -O2 -flto -fuse-linker-plugin
-fno-fat-lto-objects  (internal compiler error)
FAIL: gcc.dg/torture/arm-fp16-ops-4.c   -O2 -flto -fuse-linker-plugin
-fno-fat-lto-objects  (test for excess errors)
FAIL: gcc.dg/torture/arm-fp16-ops-7.c   -O0  (internal compiler error)
FAIL: gcc.dg/torture/arm-fp16-ops-7.c   -O0  (test for excess errors)
FAIL: gcc.dg/torture/arm-fp16-ops-7.c   -O1  (internal compiler error)
FAIL: gcc.dg/torture/arm-fp16-ops-7.c   -O1  (test for excess errors)
FAIL: gcc.dg/torture/arm-fp16-ops-7.c   -O2  (internal compiler error)
FAIL: gcc.dg/torture/arm-fp16-ops-7.c   -O2  (test for excess errors)
FAIL: gcc.dg/torture/arm-fp16-ops-7.c   -O3 -fomit-frame-pointer  (internal
compiler error)
FAIL: gcc.dg/torture/arm-fp16-ops-7.c   -O3 -fomit-frame-pointer  (test for
excess errors)
FAIL: gcc.dg/torture/arm-fp16-ops-7.c   -O3 -g  (internal compiler error)
FAIL: gcc.dg/torture/arm-fp16-ops-7.c   -O3 -g  (test for excess errors)
FAIL: gcc.dg/torture/arm-fp16-ops-7.c   -Os  (internal compiler error)
FAIL: gcc.dg/torture/arm-fp16-ops-7.c   -Os  (test for excess errors)
FAIL: gcc.dg/torture/arm-fp16-ops-7.c   -O2 -flto -fno-use-linker-plugin
-flto-partition=none  (internal compiler error)
FAIL: gcc.dg/torture/arm-fp16-ops-7.c   -O2 -flto -fno-use-linker-plugin
-flto-partition=none  (test for excess errors)
FAIL: gcc.dg/torture/arm-fp16-ops-7.c   -O2 -flto -fuse-linker-plugin
-fno-fat-lto-objects  (internal compiler error)
FAIL: gcc.dg/torture/arm-fp16-ops-7.c   -O2 -flto -fuse-linker-plugin
-fno-fat-lto-objects  (test for excess errors)
FAIL: gcc.dg/torture/arm-fp16-ops-8.c   -O0  (internal compiler error)
FAIL: gcc.dg/torture/arm-fp16-ops-8.c   -O0  (test for excess errors)
FAIL: gcc.dg/torture/arm-fp16-ops-8.c   -O1  (internal compiler error)
FAIL: gcc.dg/torture/arm-fp16-ops-8.c   -O1  (test for excess errors)
FAIL: gcc.dg/torture/arm-fp16-ops-8.c   -O2  (internal compiler error)
FAIL: gcc.dg/torture/arm-fp16-ops-8.c   -O2  (test for excess errors)
FAIL: gcc.dg/torture/arm-fp16-ops-8.c   -O3 -fomit-frame-pointer  (internal
compiler error)
FAIL: gcc.dg/torture/arm-fp16-ops-8.c   -O3 -fomit-frame-pointer  (test for
excess errors)
FAIL: gcc.dg/torture/arm-fp16-ops-8.c   -O3 -g  (internal compiler error)
FAIL: gcc.dg/torture/arm-fp16-ops-8.c   -O3 -g  (test for excess errors)
FAIL: gcc.dg/torture/arm-fp16-ops-8.c   -Os  (internal compiler error)
FAIL: gcc.dg/torture/arm-fp16-ops-8.c   -Os  (test for excess errors)
FAIL: gcc.dg/torture/arm-fp16-ops-8.c   -O2 -flto -fno-use-linker-plugin
-flto-partition=none  (internal compiler error)
FAIL: gcc.dg/torture/arm-fp16-ops-8.c   -O2 -flto -fno-use-linker-plugin
-flto-partition=none  (test for excess errors)
FAIL: gcc.dg/torture/arm-fp16-ops-8.c   -O2 -flto -fuse-linker-plugin
-fno-fat-lto-objects  (internal compiler error)
FAIL: gcc.dg/torture/arm-fp16-ops-8.c   -O2 -flto -fuse-linker-plugin
-fno-fat-lto-objects  (test for excess errors)

[Bug fortran/67429] [5/6 Regression] Missing part of error messages.

[pault at gcc dot gnu.org]

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=67429

--- Comment #16 from Paul Thomas <pault at gcc dot gnu.org> ---
Author: pault
Date: Fri Sep  4 18:37:50 2015
New Revision: 227500

URL: https://gcc.gnu.org/viewcvs?rev=227500&root=gcc&view=rev
Log:
2015-09-04  Manuel López-Ibáñez  <manu@gcc.gnu.org>

        PR fortran/67429
        * error.c (gfc_clear_pp_buffer): Reset last_location, otherwise
        caret lines might be skipped when actually giving a diagnostic.

Modified:
    trunk/gcc/fortran/ChangeLog
    trunk/gcc/fortran/error.c
>From gcc-bugs-return-496397-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Fri Sep 04 18:38:07 2015
Return-Path: <gcc-bugs-return-496397-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 41824 invoked by alias); 4 Sep 2015 18:38:07 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 41768 invoked by uid 48); 4 Sep 2015 18:38:04 -0000
From: "manu at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug middle-end/60725] [-Wreturn-type] false positive in trivial switch
Date: Fri, 04 Sep 2015 18:38:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: middle-end
X-Bugzilla-Version: 4.8.2
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: manu at gcc dot gnu.org
X-Bugzilla-Status: NEW
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-60725-4-TXZf8b4moC@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-60725-4@http.gcc.gnu.org/bugzilla/>
References: <bug-60725-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2015-09/txt/msg00375.txt.bz2
Content-length: 828

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=60725

--- Comment #6 from Manuel López-Ibáñez <manu at gcc dot gnu.org> ---
(In reply to Martin Sebor from comment #5)
> Not to complicate things too much, but reaching the closing } of a non-void
> function is valid in C.  What is not valid (i.e., has undefined behavior) is
> calling such a function and using its return value when none was provided
> (as in the program in comment #3).  The program in the Description, however,
> has well-defined behavior because f1's return value isn't used.

Good point. I don't know whether it is possible for the sanitizers to
distinguish between the two cases. 

Pretty sure it is not possible for the warning code, since at the time of
warning we know nothing of the callers (not even if there are any callers).
>From gcc-bugs-return-496399-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Fri Sep 04 18:41:44 2015
Return-Path: <gcc-bugs-return-496399-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 50754 invoked by alias); 4 Sep 2015 18:41:43 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 50705 invoked by uid 55); 4 Sep 2015 18:41:40 -0000
From: "pault at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug fortran/67429] [5/6 Regression] Missing part of error messages.
Date: Fri, 04 Sep 2015 18:41:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: fortran
X-Bugzilla-Version: 6.0
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: pault at gcc dot gnu.org
X-Bugzilla-Status: NEW
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: 5.3
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-67429-4-ArXZP8nGLk@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-67429-4@http.gcc.gnu.org/bugzilla/>
References: <bug-67429-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2015-09/txt/msg00377.txt.bz2
Content-length: 600

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=67429

--- Comment #17 from Paul Thomas <pault at gcc dot gnu.org> ---
Author: pault
Date: Fri Sep  4 18:41:08 2015
New Revision: 227501

URL: https://gcc.gnu.org/viewcvs?rev=227501&root=gcc&view=rev
Log:
2015-09-04  Manuel López-Ibáñez  <manu@gcc.gnu.org>

        PR fortran/67429
        * error.c (gfc_clear_pp_buffer): Reset last_location, otherwise
        caret lines might be skipped when actually giving a diagnostic.

Modified:
    branches/gcc-5-branch/gcc/fortran/ChangeLog
    branches/gcc-5-branch/gcc/fortran/error.c
>From gcc-bugs-return-496400-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Fri Sep 04 18:43:59 2015
Return-Path: <gcc-bugs-return-496400-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 65874 invoked by alias); 4 Sep 2015 18:43:58 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 65827 invoked by uid 48); 4 Sep 2015 18:43:55 -0000
From: "pault at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug fortran/67429] [5/6 Regression] Missing part of error messages.
Date: Fri, 04 Sep 2015 18:43:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: fortran
X-Bugzilla-Version: 6.0
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: pault at gcc dot gnu.org
X-Bugzilla-Status: RESOLVED
X-Bugzilla-Resolution: FIXED
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: 5.3
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: bug_status resolution
Message-ID: <bug-67429-4-0XxDcVm9Qt@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-67429-4@http.gcc.gnu.org/bugzilla/>
References: <bug-67429-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: 7bit
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2015-09/txt/msg00378.txt.bz2
Content-length: 521

https://gcc.gnu.org/bugzilla/show_bug.cgi?idg429

Paul Thomas <pault at gcc dot gnu.org> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|NEW                         |RESOLVED
         Resolution|---                         |FIXED

--- Comment #18 from Paul Thomas <pault at gcc dot gnu.org> ---
Fixed on trunk and 5-branch. Thanks for raising the PR, Dominique, and thanks
for a quick fix, Manuel.

Paul