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

Martin Sebor <msebor at gcc dot gnu.org> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
           Keywords|                            |accepts-invalid,
                   |                            |ice-on-invalid-code
             Target|                            |pdp11-aout
             Status|UNCONFIRMED                 |NEW
   Last reconfirmed|                            |2018-10-30
                 CC|                            |msebor at gcc dot gnu.org
     Ever confirmed|0                           |1

--- Comment #5 from Martin Sebor <msebor at gcc dot gnu.org> ---
Confirmed.  I get the following output with a pdp11-aout configured
cross-compiler:

$ cat t.c && gcc -S -O2 -Wall t.c

int a2 __attribute__ ((aligned (2)));
int a4 __attribute__ ((aligned (4)));
int ag __attribute__ ((aligned (65536)));

void f2(void) __attribute__ ((aligned (2)));
void f4(void) __attribute__ ((aligned (4)));
void fg(void) __attribute__ ((aligned (65536)));

void f2(void) {}
void f4(void) {}
void fg(void) {}

t.c:2:5: error: alignment of ‘a4’ is greater than maximum object file alignment
2
    2 | int a4 __attribute__ ((aligned (4)));
      |     ^~
t.c:3:5: error: alignment of ‘ag’ is greater than maximum object file alignment
2
    3 | int ag __attribute__ ((aligned (65536)));
      |     ^~


After removing the variable declarations I get an ICE:

during RTL pass: final
t.c: In function ‘f4’:
t.c:6:1: internal compiler error: in assemble_start_function, at varasm.c:1801
    6 | void f4(void) {}
      | ^~~~
0x1345817 assemble_start_function(tree_node*, char const*)
        /ssd/src/gcc/svn/gcc/varasm.c:1801
0xaf2550 rest_of_handle_final
        /ssd/src/gcc/svn/gcc/final.c:4645
0xaf28c2 execute
        /ssd/src/gcc/svn/gcc/final.c:4723
Please submit a full bug report,
with preprocessed source if appropriate.
Please include the complete backtrace with any bug report.
See <https://gcc.gnu.org/bugs/> for instructions.

Reply via email to