public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "d at teklibre dot com" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug inline-asm/39847] 16 symbolic register names generates error: more than 30 operands in 'asm' Date: Wed, 22 Apr 2009 18:31:00 -0000 [thread overview] Message-ID: <20090422183047.19415.qmail@sourceware.org> (raw) In-Reply-To: <bug-39847-17610@http.gcc.gnu.org/bugzilla/> ------- Comment #16 from d at teklibre dot com 2009-04-22 18:30 ------- @Jakub/Andrew: max_recog_operands = MIN(FIRST_PSEUDO_REGISTER*2,SOME_SANE_VALUE_DERIVED_FROM_SMASHING_THE_STACK_ON_IA64) ; // ? I certainly am not in a position to make a one line change to gcc and test it on ia64 or other insane architectures like vmx,intel avx, etc, etc... I also somehow doubt that a human could deal with 668 registers (a code generator might) this human, at least, copes with 32 registers just fine. -- http://gcc.gnu.org/bugzilla/show_bug.cgi?id=39847
next prev parent reply other threads:[~2009-04-22 18:31 UTC|newest] Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top 2009-04-22 13:48 [Bug inline-asm/39847] New: " d at teklibre dot com 2009-04-22 13:50 ` [Bug inline-asm/39847] " d at teklibre dot com 2009-04-22 14:04 ` d at teklibre dot com 2009-04-22 14:30 ` jakub at gcc dot gnu dot org 2009-04-22 14:58 ` d at teklibre dot com 2009-04-22 15:01 ` pinskia at gcc dot gnu dot org 2009-04-22 15:40 ` d at teklibre dot com 2009-04-22 15:46 ` pinskia at gcc dot gnu dot org 2009-04-22 16:53 ` aph at gcc dot gnu dot org 2009-04-22 17:24 ` d at teklibre dot com 2009-04-22 17:33 ` aph at redhat dot com 2009-04-22 17:47 ` aph at gcc dot gnu dot org 2009-04-22 17:52 ` jakub at gcc dot gnu dot org 2009-04-22 17:55 ` d at teklibre dot com 2009-04-22 18:01 ` d at teklibre dot com 2009-04-22 18:03 ` pinskia at gcc dot gnu dot org 2009-04-22 18:31 ` d at teklibre dot com [this message] 2009-04-22 18:40 ` aph at gcc dot gnu dot org 2009-04-22 19:03 ` hjl dot tools at gmail dot com 2009-04-22 19:48 ` d at teklibre dot com 2009-04-23 3:29 ` d at teklibre dot com 2009-04-23 3:45 ` d at teklibre dot com 2009-04-23 11:08 ` aph at gcc dot gnu dot org
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=20090422183047.19415.qmail@sourceware.org \ --to=gcc-bugzilla@gcc.gnu.org \ --cc=gcc-bugs@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).