On Wed, Sep 17, 2014 at 3:42 PM, Jakub Jelinek <ja...@redhat.com> wrote: > I don't like the == in there. Doesn't <target name>, being a target triplet > or something like that, always have to start with alphanumeric character, > and options always have to start with -? Thus, can't you decide from the > first character after -ftarget-options= whether it is for all or specific > target? If the character after = is whitespace or -, it will be for > all targets and > -ftarget-options=<target options> > form, otherwise it must be > -ftarget-options=<target name>=<target options> > form.
Yes, I think it would be better. This patch is just a prototype to show the main idea, so I'd like to hear if you agree with the approach. On Wed, Sep 17, 2014 at 3:19 PM, Bernd Schmidt <ber...@codesourcery.com> wrote: > I have no objections to supporting a -ftarget-options switch. I had posted a > patch a while ago that looked somewhat similar, but also contained an > automatic translation step from things like -march=x86_64 to a generic > -foffload-abi=lp64. I still think such a mechanism is desirable. I'm going to apply your patch on '-ftarget-options' stuff and check if it works together. -- Best regards, Andrey Turetskiy
