From: Jan Hubicka <hubicka@ucw.cz>
To: Ilya Verbin <iverbin@gmail.com>
Cc: Jan Hubicka <hubicka@ucw.cz>, gcc-patches@gcc.gnu.org, rguenther@suse.de
Subject: Re: Silence merge warnings on artiical types
Date: Mon, 30 Mar 2015 17:06:00 -0000 [thread overview]
Message-ID: <20150330170639.GD93920@kam.mff.cuni.cz> (raw)
In-Reply-To: <20150330153641.GA64930@msticlxl57.ims.intel.com>
> On Mon, Mar 30, 2015 at 05:02:57 +0200, Jan Hubicka wrote:
> > * lto-symtab.c (lto_symtab_merge_decls_2): Silence warnings on
> > artificial decls.
>
> Shouldn't this patch fix libgomp.c++/target-3.C in an offloading-enabled
> configuration? It still fails...
>
> libgomp/testsuite/libgomp.c++/../libgomp.c/target-2.c:27:13: warning: type 'struct .omp_data_s.7' violates one definition rule [-Wodr]
> #pragma omp parallel for reduction(+:s)
> ^
> #pragma omp parallel for reduction(+:s)
> ^
> double b[3 * x], c[3 * x], d[3 * x], e[3 * x];
> ^
> double b[3 * x], c[3 * x], d[3 * x], e[3 * x];
> ^
No, that is an different warning. Why those types are different? Is this a full warning output?
Honza
>
> -- Ilya
next prev parent reply other threads:[~2015-03-30 17:06 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-03-30 3:03 Jan Hubicka
2015-03-30 8:30 ` Richard Biener
2015-03-30 8:48 ` Jan Hubicka
2015-03-30 15:36 ` Ilya Verbin
2015-03-30 17:06 ` Jan Hubicka [this message]
2015-03-30 17:11 ` Ilya Verbin
2015-03-30 17:16 ` Jan Hubicka
2015-03-30 17:21 ` Jakub Jelinek
2015-03-30 17:23 ` Jan Hubicka
2015-03-30 17:53 ` Jason Merrill
2015-03-31 7:51 ` Silence merge warnings on artificial types Jan Hubicka
2015-03-31 13:26 ` Jason Merrill
2015-04-02 18:23 ` Ilya Verbin
2015-04-02 18:37 ` Jan Hubicka
2015-04-02 19:06 ` Jakub Jelinek
2015-04-03 13:36 ` Jakub Jelinek
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=20150330170639.GD93920@kam.mff.cuni.cz \
--to=hubicka@ucw.cz \
--cc=gcc-patches@gcc.gnu.org \
--cc=iverbin@gmail.com \
--cc=rguenther@suse.de \
/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).