public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "rguenth at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug fortran/54852] Bogus(?) warnings when compiling gfortran.dg/bind_c_vars.f90 gfortran.dg/bind_c_vars_driver.c with -flto Date: Tue, 04 Feb 2014 11:41:00 -0000 [thread overview] Message-ID: <bug-54852-4-AW74qqUfnB@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-54852-4@http.gcc.gnu.org/bugzilla/> http://gcc.gnu.org/bugzilla/show_bug.cgi?id=54852 Richard Biener <rguenth at gcc dot gnu.org> changed: What |Removed |Added ---------------------------------------------------------------------------- Keywords| |diagnostic, lto Status|WAITING |NEW --- Comment #3 from Richard Biener <rguenth at gcc dot gnu.org> --- LTO warns that /space/rguenther/src/svn/trunk/gcc/testsuite/gfortran.dg/bind_c_vars_driver.c:12:5: warning: type of 'myF90Array2D' does not match original declaration [enabled by default] /space/rguenther/src/svn/trunk/gcc/testsuite/gfortran.dg/bind_c_vars.f90:16:0: note: previously declared here /space/rguenther/src/svn/trunk/gcc/testsuite/gfortran.dg/bind_c_vars_driver.c:11:5: warning: type of 'myF90Array3D' does not match original declaration [enabled by default] /space/rguenther/src/svn/trunk/gcc/testsuite/gfortran.dg/bind_c_vars.f90:15:0: note: previously declared here which effectively means that assignments in GIMPLE between those arrays would be invalid (not array members but whole arrays). Not sure if we can create a testcase that will eventually ICE though. Usually the above also means that the arrays use different alias sets but that's safe here because the alias set of an array is that of its element (and those are compatible here). The issue is that in C a[2][3] is ARRAY_TYPE <ARRAY_TYPE <...> > but GFortran represents a(2)(3) as 1D ARRAY_TYPE <...> and thus both types are not structurally equivalent (which is why LTO warns). Not sure if this case is motivation enough to treat arrays structurally the same if their overall size is the same.
prev parent reply other threads:[~2014-02-04 11:41 UTC|newest] Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top 2012-10-07 21:46 [Bug fortran/54852] New: " dominiq at lps dot ens.fr 2013-06-29 14:50 ` [Bug fortran/54852] " dominiq at lps dot ens.fr 2014-02-04 11:39 ` dominiq at lps dot ens.fr 2014-02-04 11:41 ` rguenth at gcc dot gnu.org [this message]
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-54852-4-AW74qqUfnB@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: linkBe 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).