From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 14301 invoked by alias); 14 May 2010 07:11:07 -0000 Received: (qmail 14246 invoked by uid 48); 14 May 2010 07:10:49 -0000 Date: Fri, 14 May 2010 07:11:00 -0000 Message-ID: <20100514071049.14245.qmail@sourceware.org> X-Bugzilla-Reason: CC References: Subject: [Bug inline-asm/43998] inline assembler: can't set clobbering for input register In-Reply-To: Reply-To: gcc-bugzilla@gcc.gnu.org To: gcc-bugs@gcc.gnu.org From: "ebotcazou at gcc dot gnu dot org" Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm Precedence: bulk List-Id: List-Archive: List-Post: List-Help: Sender: gcc-bugs-owner@gcc.gnu.org X-SW-Source: 2010-05/txt/msg01483.txt.bz2 ------- Comment #12 from ebotcazou at gcc dot gnu dot org 2010-05-14 07:10 ------- > the compiler may think that "something" do not modify eax. So next assignment > may use eax ( mov eax, x ). So, "it does not make sense to have it as a > clobber" is not correct. does not it ? Andrew was saying that it doesn't make sense to consider input operands as clobbered by an inline asm, generically. > And the second, "Because the way the constraints are implemented inside GCC, > an input constraint cannot overlap with a clobber." - It definitely the bug. No, it isn't, it's clearly stated in the manual: "You may not write a clobber description in a way that overlaps with an input or output operand." -- ebotcazou at gcc dot gnu dot org changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |ebotcazou at gcc dot gnu dot | |org Status|UNCONFIRMED |RESOLVED Resolution| |INVALID http://gcc.gnu.org/bugzilla/show_bug.cgi?id=43998