public inbox for gcc-prs@sourceware.org help / color / mirror / Atom feed
From: "Vladimir Merzliakov" <wanderer@rsu.ru> To: nobody@gcc.gnu.org Cc: gcc-prs@gcc.gnu.org, Subject: Re: target/10327: [3.4 regression] i386 code generation problem with leal Date: Tue, 08 Apr 2003 09:06:00 -0000 [thread overview] Message-ID: <20030408090601.11745.qmail@sources.redhat.com> (raw) The following reply was made to PR target/10327; it has been noted by GNATS. From: "Vladimir Merzliakov" <wanderer@rsu.ru> To: <gcc-gnats@gcc.gnu.org>, <gcc-bugs@gcc.gnu.org>, <lucier@math.purdue.edu>, <felix@call-with-current-continuation.org>, <nobody@gcc.gnu.org>, <gcc-prs@gcc.gnu.org> Cc: Subject: Re: target/10327: [3.4 regression] i386 code generation problem with leal Date: Tue, 8 Apr 2003 13:02:15 +0400 This is a multi-part message in MIME format. ------=_NextPart_000_0082_01C2FDCF.1417B1F0 Content-Type: text/plain; charset="koi8-r" Content-Transfer-Encoding: 7bit Not fixed in current CVS version gcc version 3.4 20030408 (experimental) I have small testcase: -8X---------------------- struct s { int m1; short m2; }; void f(void) { static struct s s0; s0.m2 += 17; } -8X---------------------- Error message: /var/tmp//ccVdOHXP.s: Assembler messages: /var/tmp//ccVdOHXP.s:12: Error: suffix or operands invalid for `lea' Used options: gcc -fPIC -O -march=pentium2 test.c http://gcc.gnu.org/cgi-bin/gnatsweb.pl?cmd=view%20audit-trail&database=gcc&p r=10327 ------=_NextPart_000_0082_01C2FDCF.1417B1F0 Content-Type: application/octet-stream; name="test.s" Content-Transfer-Encoding: quoted-printable Content-Disposition: attachment; filename="test.s" .file "test.c"=0A= .local s0.0=0A= .comm s0.0,8,4=0A= .text=0A= .globl f=0A= .type f, @function=0A= f:=0A= pushl %ebp=0A= movl %esp, %ebp=0A= call __i686.get_pc_thunk.cx=0A= addl $_GLOBAL_OFFSET_TABLE_, %ecx=0A= addw $17, 4+s0.0@GOTOFF(%ecx)=0A= popl %ebp=0A= ret=0A= .size f, .-f=0A= .section .gnu.linkonce.t.__i686.get_pc_thunk.cx,"ax",@progbits=0A= .globl __i686.get_pc_thunk.cx=0A= .hidden __i686.get_pc_thunk.cx=0A= .type __i686.get_pc_thunk.cx, @function=0A= __i686.get_pc_thunk.cx:=0A= movl (%esp), %ecx=0A= ret=0A= .ident "GCC: (GNU) 3.4 20030407 (experimental)"=0A= ------=_NextPart_000_0082_01C2FDCF.1417B1F0 Content-Type: application/octet-stream; name="test.i" Content-Transfer-Encoding: quoted-printable Content-Disposition: attachment; filename="test.i" # 1 "test.c"=0A= # 1 "<built-in>"=0A= # 1 "<command line>"=0A= # 1 "test.c"=0A= struct s {=0A= int m1;=0A= short m2;=0A= };=0A= =0A= void f(void)=0A= {=0A= static struct s s0;=0A= =0A= s0.m2 +=3D 17;=0A= }=0A= ------=_NextPart_000_0082_01C2FDCF.1417B1F0--
next reply other threads:[~2003-04-08 9:06 UTC|newest] Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top 2003-04-08 9:06 Vladimir Merzliakov [this message] 2003-04-08 13:01 hubicka
Reply instructions: You may reply publicly to this message via plain-text email using any one of the following methods: * Save the following mbox file, import it into your mail client, and reply-to-all from there: mbox Avoid top-posting and favor interleaved quoting: https://en.wikipedia.org/wiki/Posting_style#Interleaved_style * Reply using the --to, --cc, and --in-reply-to switches of git-send-email(1): git send-email \ --in-reply-to=20030408090601.11745.qmail@sources.redhat.com \ --to=wanderer@rsu.ru \ --cc=gcc-prs@gcc.gnu.org \ --cc=nobody@gcc.gnu.org \ /path/to/YOUR_REPLY https://kernel.org/pub/software/scm/git/docs/git-send-email.html * If your mail client supports setting the In-Reply-To header via mailto: links, try the mailto: linkBe sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions for how to clone and mirror all data and code used for this inbox; as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).