From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 30302 invoked by alias); 2 Nov 2010 18:59:09 -0000 Received: (qmail 30291 invoked by uid 22791); 2 Nov 2010 18:59:08 -0000 X-SWARE-Spam-Status: No, hits=-2.4 required=5.0 tests=ALL_TRUSTED,AWL,BAYES_00,MISSING_MID X-Spam-Check-By: sourceware.org Received: from localhost (HELO gcc.gnu.org) (127.0.0.1) by sourceware.org (qpsmtpd/0.43rc1) with ESMTP; Tue, 02 Nov 2010 18:59:05 +0000 From: "pinskia at gcc dot gnu.org" To: gcc-bugs@gcc.gnu.org Subject: [Bug target/46275] -masm=intel -fPIC causes global offset table issues X-Bugzilla-Reason: CC X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: gcc X-Bugzilla-Component: target X-Bugzilla-Keywords: X-Bugzilla-Severity: normal X-Bugzilla-Who: pinskia at gcc dot gnu.org X-Bugzilla-Status: UNCONFIRMED X-Bugzilla-Priority: P3 X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org X-Bugzilla-Target-Milestone: --- X-Bugzilla-Changed-Fields: In-Reply-To: References: X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/ Auto-Submitted: auto-generated Content-Type: text/plain; charset="UTF-8" MIME-Version: 1.0 Date: Tue, 02 Nov 2010 18:59:00 -0000 Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm Precedence: bulk List-Id: List-Archive: List-Post: List-Help: Sender: gcc-bugs-owner@gcc.gnu.org X-SW-Source: 2010-11/txt/msg00191.txt.bz2 Message-ID: <20101102185900.yRCooMAgkYgAWJqAiVNDGNlDWS8FOQ7LNQZ-3PzQPJ4@z> http://gcc.gnu.org/bugzilla/show_bug.cgi?id=46275 --- Comment #4 from Andrew Pinski 2010-11-02 18:59:00 UTC --- -masm=intel is really only needed if you are going to do some post processing of the assembly code or want to read the assembly code in the Intel (non AT&T) format. It should not change the code generation or the ABI. Also it should be noted that the Intel compiler under GNU/Linux outputs assembly code in the AT&T format by default. Also note the generated object files will be the same. >>From what you mentioned in comment #3, I don't see a reason to use -masm=intel. Do you post process the assembly code?