From: Philip Herron <redbrain@gcc.gnu.org>
To: "Manuel López-Ibáñez" <lopezibanez@gmail.com>
Cc: "gcc-help@gcc.gnu.org" <gcc-help@gcc.gnu.org>
Subject: Re: lang.opts help
Date: Mon, 01 Jul 2013 09:14:00 -0000 [thread overview]
Message-ID: <CAEvRbeoByr1D7DqtaynZLp1_as04WEDWVea4CjaNFhfu_OEkYg@mail.gmail.com> (raw)
In-Reply-To: <CAESRpQB6xeyd1idRyf7UXY+Sroy=EcvAfOZ9KCVVD+Hm_xKQbg@mail.gmail.com>
Yeah there is a patch in the list somewhere from ages ago where me and
Andi Hellmund added huge front-end documentation but it never got
reviewed.
I think i need to resurrect this again this week and fix it up and get it in.
--Phil
On 30 June 2013 22:51, Manuel López-Ibáñez <lopezibanez@gmail.com> wrote:
> Perhaps it should be documented somewhere, but where? To be honest, if
> I had to implement a GCC FE, I wouldn't even know where to start
> looking.
>
> BTW, don't look to Fortran for a good example of how to handle
> options. Fortran duplicates the common machinery, which does a lot
> more than the Fortran implementation. The same applies to diagnostics,
> don't follow Fortran, use the common machinery. In general, the C++ FE
> is probably the most modern and the best example to look at.
>
>
>
> On 30 June 2013 22:17, Philip Herron <redbrain@gcc.gnu.org> wrote:
>> Thanks so much i just never noticed this lang hook just needed to
>> return the option_lang_mask and now its all fine.
>>
>> Thanks
>>
>> --Phil
>>
>> On 28 June 2013 19:46, Manuel López-Ibáñez <lopezibanez@gmail.com> wrote:
>>>> I have been having trouble with my lang.opts i keep getting:
>>>>
>>>> hilips-MacBook:gccpy-build redbrain$ gccpy -O0 -fdump-tree-gimple t.py
>>>> -o t.o -fpy-dump-dot -fpy-gen-main
>>>> gpy1: warning: command line option =91-fpy-dump-dot=92 is valid for Python
>>>> but not for [enabled by default]
>>>> gpy1: warning: command line option =91-fpy-gen-main=92 is valid for Python
>>>> but not for [enabled by default]
>>>> gpy1: warning: command line option
>>>> =91-L/usr/local/lib/gcc/x86_64-apple-darwin12.3.0/4.8.0=92 is valid for
>>>> Go/Python but not for [enabled by default]
>>>> gpy1: warning: command line option
>>>> =91-L/usr/local/lib/gcc/x86_64-apple-darwin12.3.0/4.8.0/../../..=92 is
>>>> valid for Go/Python but not for [enabled by default]
>>>
>>> Does your python_handle_option returns true for recognized options?
>>>
>>> When you build, in the build/gcc/ directory there is an options.c
>>> file. Does it mention Python in lang_names? Do the options have the
>>> CL_Python flag?
>>>
>>> Have you defined a hook that returns the lang_mask for Python? See Fortran:
>>>
>>> fortran/f95-lang.c:#define LANG_HOOKS_OPTION_LANG_MASK gfc_option_lang_mask
>>>
>>> BTW, you don't need to re-define Common options unless you want to
>>> completely change their meaning, which normally is a bad idea.
>>> Normally you can just re-use the results returned by the common
>>> options machinery for your own purposes.
>>>
>>> Cheers,
>>>
>>> Manuel.
next prev parent reply other threads:[~2013-07-01 9:14 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-06-29 13:02 Manuel López-Ibáñez
[not found] ` <CAEvRbepEE3MVPhwtYSHfw25YHqpZpE=v81yNBJCikBiym6knuQ@mail.gmail.com>
[not found] ` <CAESRpQB6xeyd1idRyf7UXY+Sroy=EcvAfOZ9KCVVD+Hm_xKQbg@mail.gmail.com>
2013-07-01 9:14 ` Philip Herron [this message]
2013-07-01 10:08 ` Manuel López-Ibáñez
2013-07-01 13:43 ` Philip Herron
-- strict thread matches above, loose matches on Subject: below --
2013-06-28 20:01 Philip Herron
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=CAEvRbeoByr1D7DqtaynZLp1_as04WEDWVea4CjaNFhfu_OEkYg@mail.gmail.com \
--to=redbrain@gcc.gnu.org \
--cc=gcc-help@gcc.gnu.org \
--cc=lopezibanez@gmail.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).