bug-binutils
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

[Bug gas/19614] New: gas for c6x prints "Error: inconsistent uses of .cf


From: dhowells at redhat dot com
Subject: [Bug gas/19614] New: gas for c6x prints "Error: inconsistent uses of .cfi_sections" when gcc compiles things with it
Date: Thu, 11 Feb 2016 15:13:18 +0000

https://sourceware.org/bugzilla/show_bug.cgi?id=19614

            Bug ID: 19614
           Summary: gas for c6x prints "Error: inconsistent uses of
                    .cfi_sections" when gcc compiles things with it
           Product: binutils
           Version: 2.26
            Status: NEW
          Severity: normal
          Priority: P2
         Component: gas
          Assignee: unassigned at sourceware dot org
          Reporter: dhowells at redhat dot com
  Target Milestone: ---

When gcc is building for c6x with a command like the following:

   echo 'int main() { return 0; }' | ./gcc/xgcc -x c -c -g - -B ./gcc
-fexceptions

the following occurs with the 2.26 gas:

   /tmp/cc6wIVaX.s: Assembler messages:
   /tmp/cc6wIVaX.s:12: Error: inconsistent uses of .cfi_sections

The problem is the following in the assembly source output by gcc:

...
        .cfi_sections   .debug_frame
...
        .cfi_sections .debug_frame, .c6xabi.exidx
...

If the first directive is modified to have the same parameter as the second
then the error goes away.

This isn't a problem in 2.25 and is due to the following commit:

    commit 2f0c68f23bb3132cd5ac466ca8775c0d9e4960cd
    Author: Catherine Moore <address@hidden>
    Date:   Thu May 28 14:50:36 2015 -0700
    Compact EH Support

adding a check:

  if (cfi_sections_set && cfi_sections != sections)
    as_bad (_("inconsistent uses of .cfi_sections"));

Can the check be relaxed so that if the parameter hasn't been specified yet,
it's made retroactive, but only incurs an error if changed once specified?

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

-- 
You are receiving this mail because:
You are on the CC list for the bug.


reply via email to

[Prev in Thread] Current Thread [Next in Thread]