public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "burnus at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug libgomp/60670] omp.h may differ between multilibs
Date: Fri, 04 Apr 2014 15:16:00 -0000 [thread overview]
Message-ID: <bug-60670-4-Y79nOe8Elq@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-60670-4@http.gcc.gnu.org/bugzilla/>
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=60670
Tobias Burnus <burnus at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |burnus at gcc dot gnu.org
--- Comment #3 from Tobias Burnus <burnus at gcc dot gnu.org> ---
(In reply to ro@CeBiTec.Uni-Bielefeld.DE from comment #2)
> > --- Comment #1 from Richard Biener <rguenth at gcc dot gnu.org> ---
> > Or the header needs to include all variants with proper #ifdef-ery
>
> This is difficult for a header generated per multilib at build time.
A similar issue potentially arises for OpenMP's Fortran libraries under
finclude/, i.e. omp_lib.h, omp_lib.f90, omp_lib.mod, omp_lib_kinds.mod.
Recall that the module files (.mod) are not preprocessed - and the .h files are
not if one uses "include 'omp_lib'" (instead of "#include")
However, I think for currently used type there should be no problem (with
all/most targets).
next prev parent reply other threads:[~2014-04-04 15:16 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-03-26 14:23 [Bug libgomp/60670] New: " ro at gcc dot gnu.org
2014-03-28 9:24 ` [Bug libgomp/60670] " rguenth at gcc dot gnu.org
2014-03-28 9:27 ` ro at CeBiTec dot Uni-Bielefeld.DE
2014-04-04 14:32 ` ro at gcc dot gnu.org
2014-04-04 15:16 ` burnus at gcc dot gnu.org [this message]
2014-04-04 15:20 ` ro at CeBiTec dot Uni-Bielefeld.DE
2014-04-22 11:38 ` jakub at gcc dot gnu.org
2014-06-12 19:13 ` jacknagel at gmail dot com
2014-07-16 13:30 ` jakub at gcc dot gnu.org
2014-10-30 10:41 ` jakub at gcc dot gnu.org
2015-02-10 19:10 ` pinskia at gcc dot gnu.org
2015-06-26 20:01 ` jakub at gcc dot gnu.org
2015-06-26 20:31 ` jakub at gcc dot gnu.org
2015-06-26 21:21 ` pinskia at gcc dot gnu.org
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=bug-60670-4-Y79nOe8Elq@http.gcc.gnu.org/bugzilla/ \
--to=gcc-bugzilla@gcc.gnu.org \
--cc=gcc-bugs@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).