> Step 3: Start making the case upstream with the gcc SC, or at least try. > As you've pointed out, it takes forever to get rid of an option > or change it in gcc, which is understandable in a way, so why not > start sooner than later, right? :-)
Exactly. > The latter is ugly code, IMO, but at least gas won't have a problem > with it on x86 and could be considered acceptable by some people's > definitions (regarding the $b case, though...if gas won't let it > through on linux, I see no redeeming value for making that case a > warning only situation...at least as far as we are > concerned...upstream is another matter altogether). Agreed. Martin
