[Bug libstdc++/60793] Add target *-*-dragonfly* to dg-options on 172 libstdc++ tests
redi at gcc dot gnu.org
gcc-bugzilla@gcc.gnu.org
Mon Apr 14 14:07:00 GMT 2014
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=60793
--- Comment #11 from Jonathan Wakely <redi at gcc dot gnu.org> ---
(In reply to Manuel López-Ibáñez from comment #9)
> > Because I interpret a full bootstrap to mean every major platform that gcc
> > supports.
That would be impossible for the majority of contributors, who don't have
access to most of the targets.
> > What does "bootstrap" mean? Just a standard build with
> > --disable-boostrap flag not used?
Yes.
> > I can test the dragonfly platform, but I
> > can't test every variety of linux, solaris, etc. for potential effects.
Noone is asking for that.
> http://gcc.gnu.org/contribute.html#testing
>
> Yes, it is exactly not using --disable-bootstrap. I am not sure what are the
> requirements for a new OS port, but I doubt you need to test every major
> platform. Perhaps you can ask that in the gcc@ mailing list.
That is definitely not a requirement.
Most of the changes needed should be restricted to target-specific code, so the
requirements for the change are pretty low. At worst it will probably only
affect FreeBSD and any issues can be solved.
If you don't care enough to post a few emails showing test results then noone
is going to be interested in supporting your target. See the
contrib/test_summary script in the source tree which makes it very simple to
do.
You could have done it in the time it's taken to explain why you're reluctant
to send your patches :-)
More information about the Gcc-bugs
mailing list