public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "pinskia at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug inline-asm/65436] Max number of extended asm +output operands currently limited to 15
Date: Tue, 17 Mar 2015 22:33:00 -0000 [thread overview]
Message-ID: <bug-65436-4-iN7TT9rTlb@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-65436-4@http.gcc.gnu.org/bugzilla/>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=65436
--- Comment #5 from Andrew Pinski <pinskia at gcc dot gnu.org> ---
(In reply to Adam Warner from comment #4)
> Yes I've hit the limit. A limit that your competition clang does not have.
>
> This is not a theoretical discussion.
What kind of inline-asm are you using this for?
next prev parent reply other threads:[~2015-03-17 22:33 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-03-16 12:46 [Bug c/65436] New: Max number of extended asm +input " adam at consulting dot net.nz
2015-03-16 14:01 ` [Bug inline-asm/65436] " jakub at gcc dot gnu.org
2015-03-17 21:59 ` gccbugzilla at limegreensocks dot com
2015-03-17 22:05 ` pinskia at gcc dot gnu.org
2015-03-17 22:31 ` [Bug inline-asm/65436] Max number of extended asm +output " adam at consulting dot net.nz
2015-03-17 22:33 ` pinskia at gcc dot gnu.org [this message]
2015-03-18 1:21 ` adam at consulting dot net.nz
2015-03-21 10:14 ` gccbugzilla at limegreensocks dot com
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=bug-65436-4-iN7TT9rTlb@http.gcc.gnu.org/bugzilla/ \
--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: 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).