public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "howarth at nitro dot med dot uc dot edu" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug libfortran/43572] [4.5 Regression] FAIL: gfortran.dg/PR19872.f execution test; formatted read - wrong numbers Date: Thu, 01 Apr 2010 11:26:00 -0000 [thread overview] Message-ID: <20100401112525.28726.qmail@sourceware.org> (raw) In-Reply-To: <bug-43572-276@http.gcc.gnu.org/bugzilla/> ------- Comment #4 from howarth at nitro dot med dot uc dot edu 2010-04-01 11:25 ------- Reverting back to... TREE_PUBLIC (ic_void_ptr_var) = 0; in the proposed patch results in the missing symbols again. Can we just leave... TREE_PUBLIC (ic_void_ptr_var) = 1; and find some way to coalesce the symbols so that the failure in... FAIL: gcc.dg/tree-prof/ic-misattribution-1.c compilation, -fprofile-generate -D_PROFILE_GENERATE disappears. Lastly, any chance we can change this to a P1 so that it is fixed before the gcc 4.5 release? -- http://gcc.gnu.org/bugzilla/show_bug.cgi?id=43572
next prev parent reply other threads:[~2010-04-01 11:26 UTC|newest] Thread overview: 33+ messages / expand[flat|nested] mbox.gz Atom feed top [not found] <bug-43572-276@http.gcc.gnu.org/bugzilla/> 2010-03-31 18:08 ` [Bug libfortran/43572] " danglin at gcc dot gnu dot org 2010-04-01 9:41 ` [Bug libfortran/43572] [4.5 Regression] " burnus at gcc dot gnu dot org 2010-04-01 11:26 ` howarth at nitro dot med dot uc dot edu [this message] 2010-04-01 11:26 ` howarth at nitro dot med dot uc dot edu 2010-04-01 20:51 ` dave at hiauly1 dot hia dot nrc dot ca 2010-04-01 21:03 ` danglin at gcc dot gnu dot org 2010-04-02 2:58 ` jvdelisle at gcc dot gnu dot org 2010-04-03 17:16 ` rguenth at gcc dot gnu dot org 2010-04-06 11:38 ` rguenth at gcc dot gnu dot org 2010-04-09 20:06 ` [Bug libfortran/43572] [4.5/4.6 " dave at hiauly1 dot hia dot nrc dot ca 2010-04-10 8:45 ` ramana at gcc dot gnu dot org 2010-04-12 15:50 ` ramana at gcc dot gnu dot org 2010-04-12 16:00 ` rguenth at gcc dot gnu dot org 2010-04-12 16:03 ` dave at hiauly1 dot hia dot nrc dot ca 2010-04-12 17:22 ` ramana at gcc dot gnu dot org 2010-04-15 13:44 ` dave at hiauly1 dot hia dot nrc dot ca 2010-04-15 18:40 ` ramana at gcc dot gnu dot org 2010-04-16 7:47 ` [Bug tree-optimization/43572] " ramana at gcc dot gnu dot org 2010-04-16 8:59 ` rguenth at gcc dot gnu dot org 2010-04-16 10:00 ` rguenth at gcc dot gnu dot org 2010-04-16 10:54 ` rguenth at gcc dot gnu dot org 2010-04-16 13:22 ` rguenth at gcc dot gnu dot org 2010-04-16 15:00 ` [Bug tree-optimization/43572] [4.5 " rguenth at gcc dot gnu dot org 2010-04-19 9:06 ` ramana at gcc dot gnu dot org 2010-04-19 9:13 ` rguenth at gcc dot gnu dot org 2010-04-19 9:14 ` rguenth at gcc dot gnu dot org 2010-04-20 23:34 ` mikpe at it dot uu dot se 2010-04-21 7:52 ` mikpe at it dot uu dot se 2010-04-21 8:48 ` rguenther at suse dot de 2010-04-23 1:24 ` mikpe at it dot uu dot se 2010-04-23 15:47 ` rguenth at gcc dot gnu dot org 2010-04-23 15:48 ` rguenth at gcc dot gnu dot org 2010-04-26 23:47 ` pinskia 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=20100401112525.28726.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: 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).