From: Andi Hellmund <mail@andihellmund.com>
To: charfi asma <charfiasma@yahoo.fr>
Cc: gcc-help@gcc.gnu.org
Subject: Re: [gcc front end] add options
Date: Tue, 01 Feb 2011 16:40:00 -0000 [thread overview]
Message-ID: <4D48375E.1020104@andihellmund.com> (raw)
In-Reply-To: <627793.44296.qm@web28514.mail.ukl.yahoo.com>
On 2/1/2011 4:43 PM, charfi asma wrote:
> Hello,
>
> I built a new gcc front end
> I would like to use the -fopenmp options when compiling my source file
> I could use the C front end options like -S -fdump-tree-all -O*, .... but when I
> use -fopenmp I get this error:
>
> uml1: warning: command line option â-fopenmpâ is valid for
> C/C++/Fortran/ObjC/ObjC++ but not for [enabled by default]
>
> should I modify my lang-specs.h ? If yes what kind of modification ?
>
> here is its content:
>
> {".uml", "@uml", 0, 1, 0},
> {"@uml", "uml1 %i %(invoke_as)", 0, 1, 0},
> {"@uml", "uml1 %i %(cc1_options) %{!fsyntax-only:%(invoke_as)}",
> 0, 1, 0},
>
>
> thank you very much
>
> Asma
>
Hey Asma,
I think adding -fopenmp to lang-specs.h wouldn't help since the error
message comes from uml1 (compiler proper). And by the way, the -f*
options are usually already included in %{cc1_options}. The original
definition of the -fopenmp option is available in c.opt (in c-family
directory of 4.6), but please have a look at the lang.opt file of the
Fortran front-end for details. This is how this is implemented there:
fopenmp
Fortran
; Documented in C
This then allows the Fortran front-end to "reuse" the definition of the
C (family) front-ends.
Best regards,
Andre-Marcel
next prev parent reply other threads:[~2011-02-01 16:40 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-02-01 15:43 charfi asma
2011-02-01 16:40 ` Andi Hellmund [this message]
2011-02-01 18:07 ` Philip Herron
2011-02-03 18:24 ` Re : " charfi asma
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=4D48375E.1020104@andihellmund.com \
--to=mail@andihellmund.com \
--cc=charfiasma@yahoo.fr \
--cc=gcc-help@gcc.gnu.org \
/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).