From: "Martin Liška" <mliska@suse.cz>
To: Gerald Pfeifer <gerald@pfeifer.com>, Aldy Hernandez <aldyh@redhat.com>
Cc: gcc-patches@gcc.gnu.org
Subject: Re: [patch] multi-range implementation for value_range (irange)
Date: Mon, 10 Aug 2020 05:42:13 +0200 [thread overview]
Message-ID: <83e8e27a-b49d-64e4-8a98-ee438512c3a5@suse.cz> (raw)
In-Reply-To: <alpine.LSU.2.22.394.2008051621120.4637@anthias.pfeifer.com>
On 8/5/20 4:27 PM, Gerald Pfeifer wrote:
> Hi Aldy,
>
> On Fri, 31 Jul 2020, Aldy Hernandez via Gcc-patches wrote:
>> Jeff approved this patch off-list. I will re-run tests once again and
>> commit by Monday.
>
> I believe this has broken the bootstrap with clang (specifically
> FreeBSD clang version 10.0.0):
>
> In file included from /scratch/tmp/gerald/GCC-HEAD/gcc/c/gimple-parser.c:44:
> In file included from /scratch/tmp/gerald/GCC-HEAD/gcc/tree-vrp.h:23:
> /scratch/tmp/gerald/GCC-HEAD/gcc/value-range.h:347:1: error: static declaration of 'gt_ggc_mx' follows non-static declaration gt_ggc_mx (int_range<N> *x)
> /scratch/tmp/gerald/GCC-HEAD/gcc/value-range.h:150:37: note: previous declaration is here
> template <unsigned X> friend void gt_ggc_mx (int_range<X> *);
> ^
>
> /scratch/tmp/gerald/GCC-HEAD/gcc/value-range.h:358:1: error: static declaration of 'gt_pch_nx' follows non-static declaration gt_pch_nx (int_range<N> *x)
> /scratch/tmp/gerald/GCC-HEAD/gcc/value-range.h:151:37: note: previous declaration is here
> template <unsigned X> friend void gt_pch_nx (int_range<X> *);
> ^
>
> My daily tester started to 20200803T1640, so the root cause of this must
> have entered GCC trunk between Sunday 16:40 UTC and Monday 16:40 UTC.
>
> Gerald
>
Hey.
This one is still broken. Can you please Aldy take a look?
It's good that GCC code base can be compiled with clang ;)
Martin
next prev parent reply other threads:[~2020-08-10 3:42 UTC|newest]
Thread overview: 54+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-07-31 21:44 Aldy Hernandez
2020-08-05 14:27 ` Gerald Pfeifer
2020-08-05 15:45 ` Aldy Hernandez
2020-08-05 22:43 ` Gerald Pfeifer
2020-08-06 4:00 ` Richard Sandiford
2020-08-10 3:42 ` Martin Liška [this message]
2020-08-10 7:44 ` Aldy Hernandez
2020-08-10 10:22 ` Gerald Pfeifer
2020-08-10 10:30 ` Martin Liška
2020-08-10 11:03 ` Aldy Hernandez
2020-08-05 15:09 ` std:vec for classes with constructor? (Was: Re: [patch] multi-range implementation for value_range (irange)) Martin Jambor
2020-08-05 15:41 ` Aldy Hernandez
2020-08-05 16:55 ` Richard Biener
2020-08-24 21:53 ` Jeff Law
2020-08-24 22:03 ` Andrew MacLeod
2020-08-05 16:54 ` Richard Biener
2020-08-06 1:07 ` Andrew MacLeod
2020-08-06 5:16 ` std:vec for classes with constructor? Richard Sandiford
2020-08-06 10:19 ` Jonathan Wakely
2020-08-06 10:31 ` Richard Biener
2020-08-06 10:48 ` Jonathan Wakely
2020-08-06 14:17 ` Aldy Hernandez
2020-08-06 14:35 ` Richard Biener
2020-08-06 14:59 ` Aldy Hernandez
2020-08-06 16:30 ` Jonathan Wakely
2020-08-06 17:58 ` Aldy Hernandez
2020-08-06 19:24 ` Jonathan Wakely
2020-08-07 6:48 ` Richard Biener
2020-08-07 7:57 ` Jonathan Wakely
2020-08-07 8:22 ` Richard Biener
2020-08-07 8:34 ` Jonathan Wakely
2020-08-07 8:54 ` Richard Biener
2020-08-07 8:55 ` Jakub Jelinek
2020-08-07 9:17 ` Jonathan Wakely
2020-08-07 18:04 ` Aldy Hernandez
2020-08-07 18:33 ` Jakub Jelinek
2020-08-10 12:57 ` Aldy Hernandez
2020-08-10 13:05 ` Aldy Hernandez
2020-08-10 18:03 ` Jakub Jelinek
2020-08-10 13:51 ` Jakub Jelinek
2020-08-10 16:58 ` Richard Biener
2020-08-10 17:18 ` Jakub Jelinek
2020-08-13 11:38 ` r11-2663 causes static_assert failure (was: Re: std:vec for classes with constructor?) Tobias Burnus
2020-08-13 11:52 ` Jakub Jelinek
2020-08-13 12:06 ` r11-2663 causes static_assert failure Tobias Burnus
2020-08-13 12:25 ` Jakub Jelinek
2020-08-13 12:40 ` Jakub Jelinek
2020-08-13 12:46 ` Iain Sandoe
2020-08-13 12:55 ` Iain Sandoe
2020-08-13 13:04 ` Jakub Jelinek
2020-08-13 13:00 ` Jakub Jelinek
2020-08-06 6:57 ` std:vec for classes with constructor? (Was: Re: [patch] multi-range implementation for value_range (irange)) Richard Biener
2020-08-06 10:23 ` Jonathan Wakely
2020-08-06 11:03 ` Aldy Hernandez
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=83e8e27a-b49d-64e4-8a98-ee438512c3a5@suse.cz \
--to=mliska@suse.cz \
--cc=aldyh@redhat.com \
--cc=gcc-patches@gcc.gnu.org \
--cc=gerald@pfeifer.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).