This is the mail archive of the gcc-bugs@gcc.gnu.org mailing list for the GCC project.


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]
Other format: [Raw text]

[Bug c/12122] New: gcc do not respect stack argument list order


PLEASE REPLY TO gcc-bugzilla@gcc.gnu.org ONLY, *NOT* gcc-bugs@gcc.gnu.org.

http://gcc.gnu.org/bugzilla/show_bug.cgi?id=12122

           Summary: gcc do not respect stack argument list order
           Product: gcc
           Version: 3.3.1
            Status: UNCONFIRMED
          Severity: critical
          Priority: P1
         Component: c
        AssignedTo: unassigned at gcc dot gnu dot org
        ReportedBy: bland at mail dot ru
                CC: gcc-bugs at gcc dot gnu dot org

It seems like gcc do not respect reverse argument order on stack.
The program attached produces different code (therefore output) with different
optimization levels. This seriously brokes ABI. I got same results for gcc 3.2
and 3.3.1-release compillers on ia32 and sparc platforms. Try cc with -O0, -Os,
-O3. For my understanding the only right stack content produced with -O3 option.


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]