[Bug ld/10372] New: SH: ld test with sim/sh/run fails always.

View: New views
2 Messages — Rating Filter:   Alert me  

[Bug ld/10372] New: SH: ld test with sim/sh/run fails always.

by Bugzilla from sourceware-bugzilla@sourceware.org :: Rate this Message:

Reply to Author | View Threaded | Show Only this Message

ld/testsuite/ld-sh/sh.exp:"SH relaxing execution" uses simulator.
But using sim/sh/run as a simulator, it fails always, regardless of real test
results.

--
           Summary: SH: ld test with sim/sh/run fails always.
           Product: binutils
           Version: unspecified
            Status: NEW
          Severity: normal
          Priority: P2
         Component: ld
        AssignedTo: unassigned at sources dot redhat dot com
        ReportedBy: yoshii dot takashi at renesas dot com
                CC: bug-binutils at gnu dot org
 GCC build triplet: x86_64-pc-linux-gnu
  GCC host triplet: x86_64-pc-linux-gnu
GCC target triplet: sh-linux-gnu


http://sourceware.org/bugzilla/show_bug.cgi?id=10372

------- You are receiving this mail because: -------
You are on the CC list for the bug, or are watching someone who is.


_______________________________________________
bug-binutils mailing list
bug-binutils@...
http://lists.gnu.org/mailman/listinfo/bug-binutils

[Bug ld/10372] SH: ld test with sim/sh/run fails always.

by Bugzilla from sourceware-bugzilla@sourceware.org :: Rate this Message:

Reply to Author | View Threaded | Show Only this Message


------- Additional Comments From yoshii dot takashi at renesas dot com  2009-07-07 07:12 -------
Created an attachment (id=4038)
 --> (http://sourceware.org/bugzilla/attachment.cgi?id=4038&action=view)
patch to fix

There are two (1.initial stack value, 2.syscall trap No.) to be fixed.
1. sh-linux-ld doesn't seems to set .stack, so I changed the code to use .text
as a initial(and glowing lower).
2. According to sim/sh/interp.c, syscall trap has changed to 34.


--


http://sourceware.org/bugzilla/show_bug.cgi?id=10372

------- You are receiving this mail because: -------
You are on the CC list for the bug, or are watching someone who is.


_______________________________________________
bug-binutils mailing list
bug-binutils@...
http://lists.gnu.org/mailman/listinfo/bug-binutils