public inbox for gcc-prs@sourceware.org
help / color / mirror / Atom feed
From: Pete Gonzalez <gonz@ratloop.com>
To: nobody@gcc.gnu.org
Cc: gcc-prs@gcc.gnu.org,
Subject: Re: inline-asm/10396: Constraint alternatives cause error " `asm' operand requires impossible reload"
Date: Mon, 28 Apr 2003 04:06:00 -0000	[thread overview]
Message-ID: <20030428040600.6952.qmail@sources.redhat.com> (raw)

The following reply was made to PR inline-asm/10396; it has been noted by GNATS.

From: Pete Gonzalez <gonz@ratloop.com>
To: gcc-gnats@gcc.gnu.org,gcc-bugs@gcc.gnu.org,nobody@gcc.gnu.org,
 gcc-prs@gcc.gnu.org
Cc:  
Subject: Re: inline-asm/10396: Constraint alternatives cause error "
  `asm' operand requires impossible reload"
Date: Sun, 27 Apr 2003 23:56:05 -0400

 >Do you have this problem with 3.3 as well?  Many reload and
 >inline-asm problems have been fixed for 3.3, maybe your problem
 >is fixed there as well.
 
 I attempted to recompile using the latest 3.3 snapshot (20030421),
 however the build fails with this error:
 
 >gcc   -g -O2 -DIN_GCC -DCROSS_COMPILE  -W -Wall -Wwrite-strings 
 >-Wstrict-prototypes -Wmissing-prototypes -Wtraditional -pedantic 
 >-Wno-long-long   -DHAVE_CONFIG_H -DGENERATOR_FILE  -o gengtype.exe \
 >  gengtype.o gengtype-lex.o gengtype-yacc.o ../libiberty/libiberty.a
 >./gengtype
 >Signal 11
 >make[2]: *** [s-gtype] Error 139
 >make[2]: Leaving directory 
 >`/home/Administrator/DevKitAdv-Source/build-gcc/gcc'
 >make[1]: *** [all-gcc] Error 2
 >make[1]: Leaving directory `/home/Administrator/DevKitAdv-Source/build-gcc'
 >make: *** [stmp-gcc-make-all] Error 2
 
 I guess I should wait for a more stable version of the source code.
 How far off is the official 3.3 release?
 
 Thanks,
 -Pete
 


             reply	other threads:[~2003-04-28  4:06 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-04-28  4:06 Pete Gonzalez [this message]
2003-05-06  1:16 Pete Gonzalez
2003-05-13  6:29 steven

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=20030428040600.6952.qmail@sources.redhat.com \
    --to=gonz@ratloop.com \
    --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: link
Be 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).