This is the mail archive of the gcc@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]

gcc 3.3.2/mips/mabi=64 undefined refs to __udivti3 and __umodti3


Running some tests with -mabi=64 on an SGI Octane, Irix 6.5.
Working with GCC 3.3.2 baseline compiler. We've added some code that
creates new tree code and rtl; one of those mods may (or may not)
be triggering this behavior:

ld64: ERROR   33 : Unresolved text symbol "__udivti3" -- 1st referenced
by /var/tmp//ccyXCuXb.o.
ld64: ERROR   33 : Unresolved text symbol "__umodti3" -- 1st referenced
by /var/tmp//ccyXCuXb.o.

I don't see that __divti3 is implemented in libgcc2, though it is
in the documentation and in the libgcc2.ver file. Is there some way
to invoke the make to compile the implementation in libgcc2 or is
thisa missing function?

A more basic question: what's the best way to find out which statement
in the program is causing this reference to be generated? I've tried
the following.

1) compiled with -da -save-temps, in the hope that line number notes
would be placed in the rtl dump. Perhaps they're there, but I don't
know how to decode the output.

2) compiled with -fverbose-asm -S in the hope that line number comments
would be sprinkled into the .s (assembly language) file.

3) compiled with -g -c, and then ran SGI's dis utility with a switch
that supposedly prints source line info if it can.

In summary,

- is __udivti3 and __umodti3 supported on mabi=64 SGI/MIPS targets?
- should the MIPS code generator be emitting those library calls at all?
- what's the best/easiest method for finding out which source code line
  in the compiled program corresponds the generated RTL and/or assembly
  language?

thanks.


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