[Bug target/58132] New: x86-64 gcc generate wrong movabs code for intel syntax

[Bug target/58132] New: x86-64 gcc generate wrong movabs code for intel syntax

[netfirewall at gmail dot com]

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

            Bug ID: 58132
           Summary: x86-64 gcc generate wrong movabs code for intel syntax
           Product: gcc
           Version: 4.9.0
            Status: UNCONFIRMED
          Severity: normal
          Priority: P3
         Component: target
          Assignee: unassigned at gcc dot gnu.org
          Reporter: netfirewall at gmail dot com

When I compile below testcase with gcc -masm=intel -O2

--cut here--
int test(){
    long *ptr = (long*)0xFFFF800000000000;

    *ptr = -1;

    return 0;
}
--cut here--

MOVABS is incorrectly translated into "mov [rax], -1", and causes "Error:
ambiguous operand size for `mov' ".
It should be "mov QWORD PTR [rax], -1"

This may be a patch for this bug, but has not yet been approved.
http://gcc.gnu.org/ml/gcc-patches/2013-08/msg00623.html

[Bug target/58132] x86-64 gcc generate wrong movabs code for intel syntax

[ubizjak at gmail dot com]

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

Uroš Bizjak <ubizjak at gmail dot com> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Target|                            |x86
             Status|UNCONFIRMED                 |RESOLVED
                URL|                            |http://gcc.gnu.org/ml/gcc-p
                   |                            |atches/2013-08/msg00669.htm
                   |                            |l
         Resolution|---                         |FIXED
   Target Milestone|---                         |4.7.4

--- Comment #1 from Uroš Bizjak <ubizjak at gmail dot com> ---
Fixed everywhere.
>From gcc-bugs-return-427949-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Sat Aug 17 12:22:40 2013
Return-Path: <gcc-bugs-return-427949-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 17855 invoked by alias); 17 Aug 2013 12:22:40 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 17815 invoked by uid 48); 17 Aug 2013 12:22:39 -0000
From: "jakub at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/58178] variant function name was used for user defined constructor
Date: Sat, 17 Aug 2013 12:22:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: c++
X-Bugzilla-Version: 4.8.1
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: jakub 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-Flags:
X-Bugzilla-Changed-Fields: cc
Message-ID: <bug-58178-4-0eGeqDFDoQ@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-58178-4@http.gcc.gnu.org/bugzilla/>
References: <bug-58178-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: 7bit
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2013-08/txt/msg00873.txt.bz2
Content-length: 515

http://gcc.gnu.org/bugzilla/show_bug.cgi?idX178

Jakub Jelinek <jakub at gcc dot gnu.org> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |jakub at gcc dot gnu.org

--- Comment #1 from Jakub Jelinek <jakub at gcc dot gnu.org> ---
Normally both _ZN4baseC2Ev and _ZN4baseC1Ev are emitted, with the latter being
an alias for the former.  Works just fine on Linux at least.