Bugzilla will be upgraded to version 5.0. The upgrade date is tentatively scheduled for 2 December 2018, pending final testing and feedback.
Bug 587709 - gcc appears to output 64-bit code and invoke as in 32-bit mode
gcc appears to output 64-bit code and invoke as in 32-bit mode
Product: Fedora
Classification: Fedora
Component: gcc (Show other bugs)
powerpc Linux
low Severity medium
: ---
: ---
Assigned To: Jakub Jelinek
Fedora Extras Quality Assurance
Depends On:
  Show dependency treegraph
Reported: 2010-04-30 12:14 EDT by Nicholas Haggin
Modified: 2010-04-30 12:21 EDT (History)
1 user (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2010-04-30 12:21:33 EDT
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)

  None (edit)
Description Nicholas Haggin 2010-04-30 12:14:08 EDT
Description of problem:

When invoked without specifying word size (-m32 or -m64), gcc appears to default to compiling 64-bit code and then invoking the assembler in 32-bit mode.

Version-Release number of selected component (if applicable):


How reproducible:

Compile any C source file.
Actual results:

[user@localhost ~]$ gcc hello.c
/tmp/ccYn3Uv7.s: Assembler messages:
/tmp/ccYn3Uv7.s:17: Error: junk at end of line, first unrecognized character is `@'
/tmp/ccYn3Uv7.s:29: Error: syntax error; found `@' but expected `('
/tmp/ccYn3Uv7.s:29: Error: junk at end of line: `@toc(2)'
[user@localhost ~]$ 

Expected results:

[user@localhost ~]$ gcc hello.c
[user@localhost ~]$ 

Additional info:

The machine in question is a Mac Xserve G5. Originally, the ppc64-architecture packages for GCC and binutils were installed; later, the 64-bit packages were removed and the 32-bit packages were installed. A machine installed from scratch with only the 32-bit packages works correctly, making me suspect a package configuration bug of some sort.
Comment 1 Jakub Jelinek 2010-04-30 12:21:33 EDT
If you have gcc.ppc but binutils.ppc64 installed (or gcc.ppc64 and binutils.ppc), that's just a user error.  Don't do that.

Note You need to log in before you can comment on or make changes to this bug.