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

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

http://gcc.gnu.org/bugzilla/show_bug.cgi?id=60793

--- Comment #9 from Manuel López-Ibáñez <manu at gcc dot gnu.org> ---
> 
> > And for sure you will need to ping the patches several times, there are very
> > few reviewers and they are doing also 99% of the work, so they miss patches
> > all the time. 
> 
> Well, while this is the reality of the situation, it's not reasonable.  The
> threat of pinging several times per patch set when it could be several sets
> of patches is actually why other things have taken priority.  I don't what
> the solution is; I guess I was hoping the system would fix itself but it
> doesn't sound like that's happened yet.
> 

It might not be reasonable, but it is the reality, and no fix in sight. :(

> > Also, I think you will need to do a full bootstrap+testsuite, why wouldn't
> > you be able to do that? If you don't have a machine powerful enough, you may
> > contact the compile farm to install Dragonfly on a virtual machine:
> > http://gcc.gnu.org/wiki/CompileFarm
> 
> Because I interpret a full bootstrap to mean every major platform that gcc
> supports.  What does "bootstrap" mean?  Just a standard build with
> --disable-boostrap flag not used?  I can test the dragonfly platform, but I
> can't test every variety of linux, solaris, etc. for potential effects.

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.

> Does that means it's just a matter of requesting a virtual machine on the
> compile farm and having an assigned responsible to respond to potential
> fallout that shows on DF test reports only?  It looks like I would qualify
> esp. given I have commit access to three separate BSD projects (DragonFly,
> FreeBSD, and NetBSD).

I would suggest you start by posting testresults to gcc-testresults (see bottom
of http://gcc.gnu.org/install/test.html), then divide the patches
appropriately, then simply submitting like the example above. If there is
anything else you need to do, somebody will tell you. If you don't get an
answer in two weeks, ping the patch. Yes pinging is annoying. On the other
hand, it takes no effort to do it (just a quick reply, perhaps editing the
subject to mention PING, bonus point if you give a link to the original patch
in the mailing list archives).
>From gcc-bugs-return-448988-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Mon Apr 14 12:11:41 2014
Return-Path: <gcc-bugs-return-448988-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 18251 invoked by alias); 14 Apr 2014 12:11:41 -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 18200 invoked by uid 48); 14 Apr 2014 12:11:38 -0000
From: "glisse at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c/50459] alignof doesn't work on plain old constant, works with expressions containing it
Date: Mon, 14 Apr 2014 12:11: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.6.1
X-Bugzilla-Keywords: rejects-valid
X-Bugzilla-Severity: normal
X-Bugzilla-Who: glisse at gcc dot gnu.org
X-Bugzilla-Status: NEW
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: 4.10.0
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-50459-4-xBzzSiDS0A@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-50459-4@http.gcc.gnu.org/bugzilla/>
References: <bug-50459-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/msg01008.txt.bz2
Content-length: 337

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

--- Comment #4 from Marc Glisse <glisse at gcc dot gnu.org> ---
Creating a function definitely makes sense, I should have done it when I
touched the default_conversion calls. Do you think your function could also
handle the call to default_conversion (with the tests that protect it)?