public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "olga at il dot ibm dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug middle-end/34483] wo_prof_two_strs.c:56: internal compiler error: in find_new_var_of_type, at ipa-struct-reorg.c:605
Date: Mon, 21 Jan 2008 20:55:00 -0000 [thread overview]
Message-ID: <20080121204209.1006.qmail@sourceware.org> (raw)
In-Reply-To: <bug-34483-276@http.gcc.gnu.org/bugzilla/>
------- Comment #46 from olga at il dot ibm dot com 2008-01-21 20:42 -------
(In reply to comment #45)
> > Sorry pursuing this issue, but let me completely understand it: when you run
> > *with* profiling, there are two compilations and two executions. If you compile
> > first with:
> >
> > -O3 -fipa-type-escape -fwhole-program -combine -fprofile-generate
> > w_prof_global_var.c
> >
> > and run the generated executable, is it fail or not?
> Sorry for beeing unclear. If I have done the compilation in 32 bit mode (the
> default in my config), the generated executable run fine. Then I can use the
> generated info to compile with -fprofile-use in 64 bit mode (-m64). gcc does
> not complain about this dirty trick (I have no idea if it is supposed to work)
> and produces an executable that fails to run.
I do not know whether it's legal or not to use information collected by 32bits
profiling for optimizations in 64bits, most likely it's not. But it's not what
importent here.
If you run the executable generated by:
-O3 -fipa-type-escape -fwhole-program -combine -fprofile-generate
w_prof_global_var.c -m64
is it fail or not?
Olga
--
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=34483
next prev parent reply other threads:[~2008-01-21 20:42 UTC|newest]
Thread overview: 57+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-12-15 17:21 [Bug middle-end/34483] New: " danglin at gcc dot gnu dot org
2007-12-17 15:15 ` [Bug middle-end/34483] " olga at gcc dot gnu dot org
2007-12-24 2:08 ` dave at hiauly1 dot hia dot nrc dot ca
2007-12-28 14:58 ` rsandifo at gcc dot gnu dot org
2007-12-28 19:28 ` olga at gcc dot gnu dot org
2007-12-28 19:38 ` rsandifo at nildram dot co dot uk
2007-12-28 19:54 ` dave at hiauly1 dot hia dot nrc dot ca
2007-12-29 1:25 ` dave at hiauly1 dot hia dot nrc dot ca
2007-12-29 16:20 ` hjl at lucon dot org
2007-12-30 12:19 ` olga at gcc dot gnu dot org
2007-12-30 14:54 ` pinskia at gcc dot gnu dot org
2007-12-31 19:44 ` dominiq at lps dot ens dot fr
2008-01-02 13:24 ` rsandifo at nildram dot co dot uk
2008-01-02 15:16 ` dave at hiauly1 dot hia dot nrc dot ca
2008-01-02 17:26 ` dominiq at lps dot ens dot fr
2008-01-03 2:40 ` dave at hiauly1 dot hia dot nrc dot ca
2008-01-07 14:10 ` olga at gcc dot gnu dot org
2008-01-07 20:19 ` dominiq at lps dot ens dot fr
2008-01-08 16:11 ` dave at hiauly1 dot hia dot nrc dot ca
2008-01-15 14:55 ` olga at gcc dot gnu dot org
2008-01-15 20:50 ` dominiq at lps dot ens dot fr
2008-01-16 7:13 ` dave at hiauly1 dot hia dot nrc dot ca
2008-01-20 14:35 ` olga at gcc dot gnu dot org
2008-01-20 15:29 ` dominiq at lps dot ens dot fr
2008-01-20 18:10 ` olga at gcc dot gnu dot org
2008-01-20 19:27 ` dominiq at lps dot ens dot fr
2008-01-20 21:33 ` dominiq at lps dot ens dot fr
2008-01-21 14:10 ` olga at gcc dot gnu dot org
2008-01-21 14:27 ` dominiq at lps dot ens dot fr
2008-01-21 15:18 ` dominiq at lps dot ens dot fr
2008-01-21 19:10 ` olga at il dot ibm dot com
2008-01-21 19:56 ` dominiq at lps dot ens dot fr
2008-01-21 20:41 ` olga at il dot ibm dot com
2008-01-21 20:42 ` dominiq at lps dot ens dot fr
2008-01-21 20:55 ` olga at il dot ibm dot com [this message]
2008-01-21 21:43 ` dominiq at lps dot ens dot fr
2008-01-22 21:02 ` olga at il dot ibm dot com
2008-01-22 22:12 ` olga at il dot ibm dot com
2008-01-22 23:26 ` dominiq at lps dot ens dot fr
2008-01-22 23:42 ` olga at il dot ibm dot com
2008-01-22 23:50 ` dominiq at lps dot ens dot fr
2008-01-24 13:53 ` dominiq at lps dot ens dot fr
2008-01-24 16:43 ` dave at hiauly1 dot hia dot nrc dot ca
2008-01-25 0:34 ` danglin at gcc dot gnu dot org
2008-01-25 9:14 ` olga at il dot ibm dot com
2008-01-25 19:30 ` dave at hiauly1 dot hia dot nrc dot ca
2008-01-26 22:46 ` dave at hiauly1 dot hia dot nrc dot ca
2008-01-29 10:15 ` alond at il dot ibm dot com
2008-01-30 20:14 ` dave at hiauly1 dot hia dot nrc dot ca
2008-01-31 18:53 ` alond at il dot ibm dot com
2008-01-31 22:24 ` dave at hiauly1 dot hia dot nrc dot ca
2008-01-31 22:30 ` dave at hiauly1 dot hia dot nrc dot ca
2008-02-03 14:49 ` olga at gcc dot gnu dot org
2008-02-05 2:43 ` dave at hiauly1 dot hia dot nrc dot ca
2008-02-07 10:26 ` olga at gcc dot gnu dot org
2008-02-07 15:34 ` dave at hiauly1 dot hia dot nrc dot ca
2008-11-01 20:16 ` danglin at gcc dot gnu dot 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=20080121204209.1006.qmail@sourceware.org \
--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).