<html>
<head>
<meta content="text/html; charset=ISO-8859-1"
http-equiv="Content-Type">
</head>
<body text="#000000" bgcolor="#FFFFFF">
<div class="moz-cite-prefix">Hello Renato and others,<br>
<br>
On 08/27/2013 11:20 AM, Renato Golin wrote:<br>
</div>
<blockquote
cite="mid:CAMSE1kfiuWWHNreTyMsHfh6EOhKyMAg+-hM_VY7Nu7CihwZm+A@mail.gmail.com"
type="cite">
<div dir="ltr">On 27 August 2013 09:24, Dmitri Gribenko <span
dir="ltr"><<a moz-do-not-send="true"
href="mailto:gribozavr@gmail.com" target="_blank">gribozavr@gmail.com</a>></span>
wrote:<br>
<div class="gmail_extra">
<div class="gmail_quote">
<blockquote class="gmail_quote" style="margin:0px 0px 0px
0.8ex;border-left-width:1px;border-left-color:rgb(204,204,204);border-left-style:solid;padding-left:1ex">
<div class="im">On Tue, Aug 27, 2013 at 1:11 AM, Renato
Golin <<a moz-do-not-send="true"
href="mailto:renato.golin@linaro.org">renato.golin@linaro.org</a>>
wrote:<br>
> I don't have that strong an opinion to keep things
as they are, but I also<br>
> wouldn't change unless there is a good reason (or
consensus) to do so.<br>
<br>
</div>
In my opinion, consistency is a pretty good reason.<br>
</blockquote>
</div>
<br>
</div>
<div class="gmail_extra">That's where the grey area is... Do we
strive to be consistent with the previous behaviour, or with
other flags?</div>
<div class="gmail_extra"><br>
</div>
<div class="gmail_extra">The former, how it's implemented now,
is that a "strict-align" flag would taint the whole argument
list, since there was no way to "un-taint". The latter, would
change how "strict-align" behaves, being more consistent with
other flags, but less consistent with its former self.</div>
<div class="gmail_extra"><br>
</div>
<div class="gmail_extra">Jeroen, do you have any input in this?
Any special reason for not having made like other dual flags?</div>
<br>
</div>
</blockquote>
<br>
No special reason, I must have been in a good mood I guess.<br>
I would like it even more to throw an error at the user for passing<br>
such inconsistent flags, with the question to make up his / her mind<br>
and filter-out one of them. Or preferably not add them both in the<br>
first place.<br>
<br>
Luckily we don't have to discuss that, for the simple fact gcc seems<br>
to use the last flag and clang seems to follow accordingly. Patches<br>
attached, intended to match that behaviour.<br>
<br>
Regards,<br>
Jeroen<br>
<br>
<br>
<br>
</body>
</html>