From: Jan Hubicka <hubicka@ucw.cz>
To: Prathamesh Kulkarni <prathamesh.kulkarni@linaro.org>
Cc: Jan Hubicka <hubicka@ucw.cz>,
gcc Patches <gcc-patches@gcc.gnu.org>,
Richard Biener <rguenther@suse.de>
Subject: Re: [RFC] Extend ipa-bitwise-cp with pointer alignment propagation
Date: Thu, 06 Oct 2016 13:21:00 -0000 [thread overview]
Message-ID: <20161006132144.GC62712@kam.mff.cuni.cz> (raw)
In-Reply-To: <CAAgBjMkKUS+jkqQc4sRWZO=WDumTsNLH228uSAHm_UVrKAXGHQ@mail.gmail.com>
> >
> > What do you mean by "for instance?" What are the other cases when it
> > happens?
> Well ipa_get_type() returned NULL for 481.wrf, and I assumed it was a
> fortran-only
> code-base but apparently it's a mix of C and fortran.
Yep, I also have expreinece that the K&R style declarations are more common
than one would expect 30 years after the language was obsoletted.
> ipa_get_type() returned NULL for param 'n' in
> get_initial_data_value_() which is defined
> as K&R style function in wrf_num_bytes_between.c, so it seems K&R is the
> only case where ipa_get_type() returns NULL.
>
> I have a question though on how to reduce fortran test-cases or a mix
> of fortran/C
> like 481.wrf ? For C/C++ only tests-cases, I use creduce.
I use delta/multidelta
https://gcc.gnu.org/wiki/A_guide_to_testcase_reduction
It works pretty well and one can reduce first list of files and then file at a
time.
Honza
next prev parent reply other threads:[~2016-10-06 13:21 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-09-21 17:25 Prathamesh Kulkarni
2016-09-22 9:38 ` Richard Biener
2016-09-22 9:41 ` Richard Biener
2016-09-22 12:12 ` Jan Hubicka
2016-10-03 19:07 ` Prathamesh Kulkarni
2016-10-04 14:54 ` Jan Hubicka
2016-10-05 14:16 ` Martin Jambor
2016-10-06 4:55 ` Prathamesh Kulkarni
2016-10-06 13:21 ` Jan Hubicka [this message]
2016-10-06 20:55 ` Prathamesh Kulkarni
2016-10-08 17:31 ` Jan Hubicka
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=20161006132144.GC62712@kam.mff.cuni.cz \
--to=hubicka@ucw.cz \
--cc=gcc-patches@gcc.gnu.org \
--cc=prathamesh.kulkarni@linaro.org \
--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).