public inbox for gcc-prs@sourceware.org help / color / mirror / Atom feed
From: Wolfgang Bangerth <bangerth@ticam.utexas.edu> To: nobody@gcc.gnu.org Cc: gcc-prs@gcc.gnu.org, Subject: Re: middle-end/8147: Erroneous Duplicate Symbols in GCJ (fwd) Date: Sat, 15 Mar 2003 16:36:00 -0000 [thread overview] Message-ID: <20030315163601.9347.qmail@sources.redhat.com> (raw) The following reply was made to PR middle-end/8147; it has been noted by GNATS. From: Wolfgang Bangerth <bangerth@ticam.utexas.edu> To: gcc-gnats@gcc.gnu.org Cc: Subject: Re: middle-end/8147: Erroneous Duplicate Symbols in GCJ (fwd) Date: Sat, 15 Mar 2003 10:31:48 -0600 (CST) ---------- Forwarded message ---------- Date: Sat, 15 Mar 2003 07:00:36 -0700 From: Jim Redman <jredman@ergotech.com> To: bangerth@dealii.org Subject: Re: middle-end/8147: Erroneous Duplicate Symbols in GCJ Wolfgang, It's a 2.x bug. I haven't seen it in the 3.x series - I think it's safe to close it. Thanks, Jim On 2003.03.14 20:35 bangerth@dealii.org wrote: > Synopsis: Erroneous Duplicate Symbols in GCJ > > State-Changed-From-To: open->feedback > State-Changed-By: bangerth > State-Changed-When: Sat Mar 15 03:35:17 2003 > State-Changed-Why: > Too bad nobody has looked at this by now... > > In any case, two questions: > - does this still happen with more recent versions of gcc, > say 3.2.2? > - in order to fix it, we need a complete testcase, i.e. > with all module import statements, etc (or whatever the > correct java-speak for this is :-). Please review > http://gcc.gnu.org/bugs.html > for this. > > Thanks > Wolfgang > > http://gcc.gnu.org/cgi-bin/gnatsweb.pl?cmd=view%20audit-trail&database=gcc&pr=8147 > -- Jim Redman (505) 662 5156 http://www.ergotech.com
reply other threads:[~2003-03-15 16:36 UTC|newest] Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=20030315163601.9347.qmail@sources.redhat.com \ --to=bangerth@ticam.utexas.edu \ --cc=gcc-prs@gcc.gnu.org \ --cc=nobody@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).