public inbox for gcc-prs@sourceware.org
help / color / mirror / Atom feed
* libgcj/8998: permission checking problems in resolve.cc
@ 2002-12-18 14:36 tromey
0 siblings, 0 replies; 2+ messages in thread
From: tromey @ 2002-12-18 14:36 UTC (permalink / raw)
To: gcc-gnats
>Number: 8998
>Category: libgcj
>Synopsis: permission checking problems in resolve.cc
>Confidential: no
>Severity: serious
>Priority: medium
>Responsible: unassigned
>State: open
>Class: sw-bug
>Submitter-Id: net
>Arrival-Date: Wed Dec 18 14:36:00 PST 2002
>Closed-Date:
>Last-Modified:
>Originator: Tom Tromey
>Release: unknown-1.0
>Organization:
>Environment:
>Description:
Per reported some potential problems with the
permission checking code in resolve.cc:
http://gcc.gnu.org/ml/java-patches/2002-q4/msg00373.html
This needs to be investigated and fixed for 3.3.
>How-To-Repeat:
>Fix:
>Release-Note:
>Audit-Trail:
>Unformatted:
^ permalink raw reply [flat|nested] 2+ messages in thread
* Re: libgcj/8998: permission checking problems in resolve.cc
@ 2002-12-20 12:27 tromey
0 siblings, 0 replies; 2+ messages in thread
From: tromey @ 2002-12-20 12:27 UTC (permalink / raw)
To: gcc-bugs, gcc-prs, java-prs, nobody, tromey, tromey
Synopsis: permission checking problems in resolve.cc
Responsible-Changed-From-To: unassigned->tromey
Responsible-Changed-By: tromey
Responsible-Changed-When: Fri Dec 20 12:27:32 2002
Responsible-Changed-Why:
I'm handling this.
State-Changed-From-To: open->closed
State-Changed-By: tromey
State-Changed-When: Fri Dec 20 12:27:32 2002
State-Changed-Why:
The code in question is confusingly written, but
correct.
http://gcc.gnu.org/cgi-bin/gnatsweb.pl?cmd=view%20audit-trail&database=gcc&pr=8998
^ permalink raw reply [flat|nested] 2+ messages in thread
end of thread, other threads:[~2002-12-20 20:27 UTC | newest]
Thread overview: 2+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2002-12-18 14:36 libgcj/8998: permission checking problems in resolve.cc tromey
2002-12-20 12:27 tromey
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).