public inbox for gcc-patches@gcc.gnu.org
 help / color / mirror / Atom feed
From: Jan Hubicka <hubicka@ucw.cz>
To: "Dominique d'Humières" <dominiq@lps.ens.fr>
Cc: hubicka@ucw.cz, rguenther@suse.de,
	Paul Richard Thomas <paul.richard.thomas@gmail.com>,
	GCC Patches <gcc-patches@gcc.gnu.org>
Subject: Re: Fix more of C/fortran canonical type issues
Date: Mon, 12 Oct 2015 07:10:00 -0000	[thread overview]
Message-ID: <20151012071042.GD70214@kam.mff.cuni.cz> (raw)
In-Reply-To: <BDE74111-F122-4E7D-8B87-00965F66041E@lps.ens.fr>

> Honza,
> > this is a variant of patch I commited (adding the suggested predicate)
> 
> This caused https://gcc.gnu.org/bugzilla/show_bug.cgi?id=67923

Hmm, strange, I do not seem to be able to reproduce this locally. Is it x86?

/opt/gcc/_clean/gcc/testsuite/gfortran.dg/pr56015.f90:12:0: error: type mismatch in pointer plus expression
   subroutine foo (p)
^
complex double[10] *

complex double[10] * restrict

long int

_85 = p_5(D) + 32;

I suppose the complaint is about "long int".  Did you possibly revert the change
to skip TYPE_CANONICAL testing in useless_type_conversion? That would declare
"long int" to be the same as "unsigned long int"

Honza

  reply	other threads:[~2015-10-12  7:10 UTC|newest]

Thread overview: 30+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-10-11  8:09 Dominique d'Humières
2015-10-12  7:10 ` Jan Hubicka [this message]
2015-10-12  7:41   ` Richard Biener
  -- strict thread matches above, loose matches on Subject: below --
2015-06-08  1:23 Jan Hubicka
2015-06-08  5:45 ` Jan Hubicka
2015-06-08  7:25   ` Jan Hubicka
2015-06-08 13:43     ` Richard Biener
2015-06-08 14:07       ` Joseph Myers
2015-06-08 14:32         ` Richard Biener
2015-06-08 14:44           ` Joseph Myers
2015-06-08 14:52             ` Jan Hubicka
2015-06-08 14:54               ` Richard Biener
2015-06-08 15:11                 ` Jan Hubicka
2015-06-09  9:50                   ` Richard Biener
2015-06-09 17:24                     ` Jan Hubicka
2015-06-11 17:58                       ` Jan Hubicka
2015-06-22  7:25                       ` Jan Hubicka
2015-06-22 15:09                         ` Richard Biener
2015-06-22 16:17                           ` Jan Hubicka
2015-06-08 15:08       ` Jan Hubicka
2015-06-08 16:54         ` Joseph Myers
2015-06-08 16:57           ` Jan Hubicka
2015-06-08 17:03             ` Joseph Myers
2015-06-08 22:06               ` Jan Hubicka
2015-06-08 23:01       ` Jan Hubicka
2015-10-08  3:47     ` Jan Hubicka
2015-10-08  7:44       ` Richard Biener
2015-10-08 16:17         ` Jan Hubicka
2015-10-10 19:45         ` Jan Hubicka
2015-06-08 13:37   ` Richard Biener

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=20151012071042.GD70214@kam.mff.cuni.cz \
    --to=hubicka@ucw.cz \
    --cc=dominiq@lps.ens.fr \
    --cc=gcc-patches@gcc.gnu.org \
    --cc=paul.richard.thomas@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).