public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: Daniel Berlin <dberlin@dberlin.org>
To: pinskia@physics.uc.edu
Cc: gcc-bugs@gcc.gnu.org
Subject: Re: [Bug ada/9953] [3.4 regression] Unsatisfied symbols: U_prep_frame_rec_for_unwind (code)
Date: Mon, 26 May 2003 02:43:00 -0000 [thread overview]
Message-ID: <Pine.LNX.4.53.0305252208530.27195@dberlin.org> (raw)
In-Reply-To: <20030526014723.14941.qmail@sources.redhat.com>
Please target 3.4 regressions at milestone 3.4, so people don't have to do
summary searches to try to determine what should be fixed for 3.4
I'm not sure it's actually necessary to mark it as a 3.4 regression in the
summary, as we could use a bug flag for regression rather than dirtying
the summary.
> What |Removed |Added
> ----------------------------------------------------------------------------
> Status|RESOLVED |UNCONFIRMED
> Resolution|FIXED |
> Summary|Unsatisfied symbols: |[3.4 regression] Unsatisfied
> |U_prep_frame_rec_for_unwind |symbols:
> |(code) |U_prep_frame_rec_for_unwind
> | |(code)
>
>
> ------- Additional Comments From pinskia@physics.uc.edu 2003-05-26 01:47 -------
> According to the submitter it is broken for 3.4, but was fixed for 3.2.3
and 3.4.
>
>
>
> ------- You are receiving this mail because: -------
> You are on the CC list for the bug, or are watching someone who is.
>
next prev parent reply other threads:[~2003-05-26 2:10 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20030304212600.9953.dave.anglin@nrc-cnrc.gc.ca>
2003-05-25 21:17 ` [Bug ada/9953] " pinskia@physics.uc.edu
2003-05-26 2:02 ` dave@hiauly1.hia.nrc.ca
2003-05-26 2:10 ` [Bug ada/9953] [3.4 regression] " pinskia@physics.uc.edu
2003-05-26 2:43 ` Daniel Berlin [this message]
2003-05-26 2:48 ` pinskia@physics.uc.edu
2003-06-03 15:12 ` hainque@act-europe.fr
2003-06-05 15:18 ` danglin@gcc.gnu.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=Pine.LNX.4.53.0305252208530.27195@dberlin.org \
--to=dberlin@dberlin.org \
--cc=gcc-bugs@gcc.gnu.org \
--cc=pinskia@physics.uc.edu \
/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).