I should also note the testsuite point I mentioned in the BoF, and related
points about building target libraries, which mean this is more
complicated than just the driver specs change:
There is testsuite logic (see gcc/testsuite/lib/atomic-dg.exp) to locate
libatomic for build-tree testing and
On Wed, 16 Aug 2017, NightStrike wrote:
> On Mon, Aug 14, 2017 at 11:10 PM, Martin Sebor wrote:
> > On 08/14/2017 04:22 PM, Eric Gallager wrote:
> >>
> >> I'm emailing this manually to the list because Bugzilla is down and I
> >> can't file a bug on Bugzilla about Bugzilla being down. The error
>
On Wed, 16 Aug 2017, Eric Gallager wrote:
> I see Richi redid all his 7.2 release changes; does that imply that
> the server restore is now complete?
No, there's still a search process ongoing to identify corrupted or
missing files by comparison with the last backup.
My expectation is that all
On Tue, 15 Aug 2017, Martin Sebor wrote:
> On 08/15/2017 10:27 AM, Joseph Myers wrote:
> > On Tue, 15 Aug 2017, Martin Sebor wrote:
> >
> > > It looks like the data loss extends beyond 8/14. Bug 81840
> > > was created Sunday afternoon but is not in t
On Tue, 15 Aug 2017, Martin Sebor wrote:
> It looks like the data loss extends beyond 8/14. Bug 81840
> was created Sunday afternoon but is not in the database:
>
> https://gcc.gnu.org/ml/gcc-bugs/2017-08/msg01303.html
>
> (Strangely, 81841 is there, as is 81839.)
That's another 81839 replac
On Mon, 15 May 2017, msebor at gcc dot gnu.org wrote:
> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=80730
>
> --- Comment #5 from Martin Sebor ---
> I"m not sure I understand what you're saying. Your comment that "the
> initializer *as
> converted* must be a constant expression (and, thus, to
On Thu, 25 Aug 2016, Nick Clifton wrote:
> gcc/ChangeLog
> 2016-08-25 Nick Clifton
>
> * config/ia64/ia64.c (ia64_init_builtins): Initialise the
> float128_type_node if that has not been done already.
> * config/i386/i386.c (ix86_init_builtin_types): Likewise.
No, this is wr
On Thu, 25 Aug 2016, Joseph Myers wrote:
> _Float128). Though preferable would be to fix all the targets with
> IX86_NO_LIBGCC_TFMODE / IX86_MAYBE_NO_LIBGCC_TFMODE /
> IA64_NO_LIBGCC_TFMODE so that they include the relevant support code in
> libgcc and so no lon
On Thu, 25 Aug 2016, Nick Clifton wrote:
> The cause appears to be an attempt to register a builtin type using
> the float128_type_node, which is NULL for these particular targets:
>
> gcc/config/ia64/ia64.c:10373
> gcc/config/i386/i386.c:33347
>
> Presumably float128_type_node sho
>Number: 928
>Category: other
>Synopsis: Out of date preprocessor docs in extend.texi
>Confidential: no
>Severity: non-critical
>Priority: low
>Responsible:unassigned
>State: open
>Class: doc-bug
>Submitter-Id: net
>Arrival-Date: Wed Nov
10 matches
Mail list logo
