This is the mail archive of the gcc-patches@gcc.gnu.org mailing list for the GCC project.

Index Nav:	[Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav:	[Date Prev] [Date Next]	[Thread Prev] [Thread Next]
Other format:	[Raw text]

Re: [PING^2] [Patch] Ignore Invalid Memory operands in constraint 'X'

From: Mike Stump <mrs at mrs dot kithrup dot com>
To: Georg-Johann Lay <gjl at gcc dot gnu dot org>
Cc: "Hurugalawadi, Naveen" <Naveen dot Hurugalawadi at caviumnetworks dot com>, "gcc-patches at gcc dot gnu dot org" <gcc-patches at gcc dot gnu dot org>
Date: Fri, 25 Jan 2013 10:02:24 -0800
Subject: Re: [PING^2] [Patch] Ignore Invalid Memory operands in constraint 'X'
References: <F3068DEED1A463459E0887A091B154933949A1@BY2PRD0710MB364.namprd07.prod.outlook.com> <51018B51.6060504@gcc.gnu.org>

On Jan 24, 2013, at 11:28 AM, Georg-Johann Lay <gjl@gcc.gnu.org> wrote:
>> Please consider this as a reminder to review the patch posted at
>> following link:-
>> http://gcc.gnu.org/ml/gcc-patches/2012-12/msg00765.html
> 
> What is this good for?
> 
> Why are you changing the semantics of an existing, global constraint?

Don't worry, we reject this patch; it is a bad idea.  X does in fact mean, place no constraints on it.  If a port wants something between X and r, then the port will define their own letter and use it.

References:
- [PING^2] [Patch] Ignore Invalid Memory operands in constraint 'X'
  - From: Hurugalawadi, Naveen
- Re: [PING^2] [Patch] Ignore Invalid Memory operands in constraint 'X'
  - From: Georg-Johann Lay

Index Nav:	[Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav:	[Date Prev] [Date Next]	[Thread Prev] [Thread Next]