[Bug debug/67855] New: -g doesn't with x86 interrupt handler

[Bug debug/67855] New: -g doesn't with x86 interrupt handler

[hjl.tools at gmail dot com]

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

            Bug ID: 67855
           Summary: -g doesn't with x86 interrupt handler
           Product: gcc
           Version: 5.3.0
            Status: UNCONFIRMED
          Severity: normal
          Priority: P3
         Component: debug
          Assignee: unassigned at gcc dot gnu.org
          Reporter: hjl.tools at gmail dot com
                CC: julia.koval at intel dot com
            Blocks: 67552
  Target Milestone: ---

[hjl@gnu-6 interrupt-1]$ cat i-2.i
__attribute__((interrupt))
void
fn (void *frame)
{
}
[hjl@gnu-6 interrupt-1]$ make i-2.s
/export/build/gnu/gcc/build-x86_64-linux/gcc/xgcc
-B/export/build/gnu/gcc/build-x86_64-linux/gcc/ -O2 -Wall -Wunused-parameter
-mno-push-args -m32 -g -S -o i-2.s i-2.i
i-2.i: In function ‘fn’:
i-2.i:5:1: internal compiler error: in vt_add_function_parameter, at
var-tracking.c:9736
 }
 ^
0x10c1da1 vt_add_function_parameter
        /export/gnu/import/git/sources/gcc/gcc/var-tracking.c:9736
0x10c2364 vt_add_function_parameters
        /export/gnu/import/git/sources/gcc/gcc/var-tracking.c:9795
0x10c2bc8 vt_initialize
        /export/gnu/import/git/sources/gcc/gcc/var-tracking.c:10012
0x10c36d7 variable_tracking_main_1
        /export/gnu/import/git/sources/gcc/gcc/var-tracking.c:10272
0x10c3801 variable_tracking_main()
        /export/gnu/import/git/sources/gcc/gcc/var-tracking.c:10325
0x10c388e execute
        /export/gnu/import/git/sources/gcc/gcc/var-tracking.c:10362
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.
Makefile:33: recipe for target 'i-2.s' failed
make: *** [i-2.s] Error 1
[hjl@gnu-6 interrupt-1]$ 

The parameter in interrupt handler is special and they don't
follow the normal psABI.


Referenced Bugs:

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=67552
[Bug 67552] [meta] x86 interrupt attribute
>From gcc-bugs-return-498794-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Mon Oct 05 17:22:33 2015
Return-Path: <gcc-bugs-return-498794-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 128618 invoked by alias); 5 Oct 2015 17:22:33 -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 123807 invoked by uid 55); 5 Oct 2015 17:22:29 -0000
From: "joseph at codesourcery dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c/67854] Missing diagnostic for passing bool to va_arg
Date: Mon, 05 Oct 2015 17:22: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: diagnostic
X-Bugzilla-Severity: normal
X-Bugzilla-Who: joseph at codesourcery 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:
Message-ID: <bug-67854-4-QIWGiMiAda@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-67854-4@http.gcc.gnu.org/bugzilla/>
References: <bug-67854-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-10/txt/msg00349.txt.bz2
Content-length: 643

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

--- Comment #1 from joseph at codesourcery dot com <joseph at codesourcery dot com> ---
I wonder if this is yet another issue with macros from system headers
(bool being defined in a system header to expand to _Bool) ... maybe we
need a systematic review of diagnostic locations in the C-family front
ends to identify such cases where the diagnostic relates to a property of
the use of the (type / expression) macro from a system header, not to a
property of that (type / expression) itself, and so system-header
suppression should only apply if the use itself is in a system header.