Evening all,
Something has changed in the last few weeks that has resulted in, as the
subject says, non-virtual thunks (in this case, all specifically to dtors, but
I don't know if that is relevant or mere accident) no longer being emitted as
comdat for i686-pc-cygwin; I haven't checked oth
Thanks for the feedback.
> Moving the test case into an attachment won't be useful. What would be
> useful is recasting the test case into a form which can be used in the
> gcc testsuite, if possible
Whilst I would like to be able to submit new test cases as I go, as
you (Ian) pointed out this m
On Thu, 6 Jan 2011, Ian Lance Taylor wrote:
> > 5. Similarly, if I mark a bug as known to work in 4.5.2, will this
> > lead to it eventually being closed?
>
> Yes, when the 4.4 release is closed, bugs known to work in 4.5 will be
> closed.
That's not how it works. I did the last couple of branc
On 7 January 2011 04:59, Tony Poppleton wrote:
> Hi,
>
> I would like to help with some gcc bug triage, and have a few
> questions about doing so.
Excellent, thanks for volunteering your time.
> For example, in cases where a bug doesn't have a test case as an
> attachment, but instead embedded in
On Thu, Jan 06, 2011 at 10:31:28PM -0800, Ian Lance Taylor wrote:
> > 2. A large number of bugs seem to not be targetted for any particular
> > release, e.g. of the 4389 open bugs, only 296 are listed as targetted
> > for 4.6.0. Why is there such a discrepency?
> >
> > Incidentally, my main focus
On 01/06/2011 09:28 PM, Gerald Pfeifer wrote:
On Thu, 6 Jan 2011, Ralf Wildenhues wrote:
Could be libtool issue or lib-link.m4 one (or gcj one). Can you send
./libtool --tag=GCJ --config
output?
I assume you mean from libjava in the build tree? Attached.
(Note this is now x86_64-portbld-
