[Bug middle-end/63943] wrong location for -Wmaybe-uninitialized in inlined function

["manu at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>]

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

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

           What    |Removed                     |Added
----------------------------------------------------------------------------
           Keywords|                            |diagnostic
             Status|UNCONFIRMED                 |NEW
   Last reconfirmed|                            |2014-11-19
                 CC|                            |manu at gcc dot gnu.org
             Blocks|                            |24639
            Summary|-Wmaybe-uninitialized       |wrong location for
                   |pragma mishandled in        |-Wmaybe-uninitialized in
                   |inlined function            |inlined function
     Ever confirmed|0                           |1
      Known to fail|                            |4.9.2, 5.0

--- Comment #1 from Manuel López-Ibáñez <manu at gcc dot gnu.org> ---
Confirmed also in GCC 5.0.

The problem is the location info that is available in the middle-end and how
this is transformed when inlining and renaming/propagating copies. To be able
to silence this, the warning should be given at the location of 'return *p'. 

We have the correct location in 028t.esra:
;;   basic block 4, loop depth 0, count 0, freq 10000, maybe hot
;;    prev block 3, next block 5, flags: (NEW, REACHABLE)
;;    pred:       2 (FALSE_VALUE,EXECUTABLE)
;;   starting at line 7
  [test.c:7:10] _9 = v$4_14(D);
  _13 = _9;
  [test.c:17:27] iftmp.0_10 = _9;
;;    succ:       5 (FALLTHRU,EXECUTABLE)

but the middle-end loses it after 030t.fre1:

;;   basic block 5, loop depth 0, count 0, freq 0, maybe hot
;;    prev block 4, next block 1, flags: (NEW, REACHABLE)
;;    pred:       3 (FALLTHRU,EXECUTABLE)
;;                4 (FALLTHRU,EXECUTABLE)
;;   starting at line -1, discriminator 4
  # iftmp.0_1 = PHI <[test.c:17:27] iftmp.0_8(3), [test.c:17:27] v$4_14(D)(4)>


As a side note, I wonder if %K could be used here to get an "inline-from"
backtrace like we do in other diagnostics.
>From gcc-bugs-return-467515-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Wed Nov 19 15:23:38 2014
Return-Path: <gcc-bugs-return-467515-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 22080 invoked by alias); 19 Nov 2014 15:23:38 -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 22030 invoked by uid 48); 19 Nov 2014 15:23:34 -0000
From: "manu at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug driver/36312] should refuse to overwrite input file with output file
Date: Wed, 19 Nov 2014 15:23:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: driver
X-Bugzilla-Version: 4.1.2
X-Bugzilla-Keywords: diagnostic, patch
X-Bugzilla-Severity: enhancement
X-Bugzilla-Who: manu at gcc dot gnu.org
X-Bugzilla-Status: REOPENED
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-36312-4-oj3m4jNZDQ@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-36312-4@http.gcc.gnu.org/bugzilla/>
References: <bug-36312-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: 2014-11/txt/msg01987.txt.bz2
Content-length: 760

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

--- Comment #16 from Manuel López-Ibáñez <manu at gcc dot gnu.org> ---
(In reply to carlos from comment #15)
> It would be sufficient if /dev/null were special cased in some way for Linux
> configurations.

There is a pre-approved patch here
(https://gcc.gnu.org/bugzilla/show_bug.cgi?id=63837#c12) that I'm testing.
Unfortunately, there seems to be a problem with the machine in the compile farm
that I use for gcc development, and I'm not able to finish a
bootstrap&regression test. I always get:

couldn't create output pipe for command: too many open files

even for a pristine copy of GCC. This didn't happen a few days ago. I didn't
have time yet to investigate what is wrong.
>From gcc-bugs-return-467516-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Wed Nov 19 15:24:11 2014
Return-Path: <gcc-bugs-return-467516-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 22846 invoked by alias); 19 Nov 2014 15:24:10 -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 22811 invoked by uid 48); 19 Nov 2014 15:24:07 -0000
From: "tbsaunde at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug lto/50687] Missing symbols with -flto -fvisibility=hidden on 4.6.x but not on 4.7.0
Date: Wed, 19 Nov 2014 15:24:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: lto
X-Bugzilla-Version: 4.6.2
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: tbsaunde at gcc dot gnu.org
X-Bugzilla-Status: RESOLVED
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_status cc resolution
Message-ID: <bug-50687-4-W5O1RrT2XM@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-50687-4@http.gcc.gnu.org/bugzilla/>
References: <bug-50687-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: 2014-11/txt/msg01988.txt.bz2
Content-length: 565

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

tbsaunde at gcc dot gnu.org changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|UNCONFIRMED                 |RESOLVED
                 CC|                            |tbsaunde at gcc dot gnu.org
         Resolution|---                         |INVALID

--- Comment #5 from tbsaunde at gcc dot gnu.org ---
both 4.6 and 4.7 are unmaintained at this point, and this seems like reasonable
behavior anyway.