[Bug libstdc++/60793] Add target *-*-dragonfly* to dg-options on 172 libstdc++ tests

["redi at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>]

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 :-)
>From gcc-bugs-return-448999-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Mon Apr 14 14:09:12 2014
Return-Path: <gcc-bugs-return-448999-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 10009 invoked by alias); 14 Apr 2014 14:09:10 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 9946 invoked by uid 48); 14 Apr 2014 14:09:04 -0000
From: "nightstrike at gmail dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c/36750] -Wmissing-field-initializers relaxation request
Date: Mon, 14 Apr 2014 14:09:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: c
X-Bugzilla-Version: 4.1.2
X-Bugzilla-Keywords: diagnostic
X-Bugzilla-Severity: enhancement
X-Bugzilla-Who: nightstrike at gmail dot com
X-Bugzilla-Status: RESOLVED
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: cc
Message-ID: <bug-36750-4-0svwA4x7zZ@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-36750-4@http.gcc.gnu.org/bugzilla/>
References: <bug-36750-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: 7bit
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2014-04/txt/msg01019.txt.bz2
Content-length: 413

http://gcc.gnu.org/bugzilla/show_bug.cgi?id6750

nightstrike <nightstrike at gmail dot com> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |nightstrike at gmail dot com

--- Comment #6 from nightstrike <nightstrike at gmail dot com> ---
This is still an issue in C++