On 12/06/2018 23:26, Martin Sebor wrote:
Bootstrap fails in libstdc++ with the following error.
I haven't investigated it much except to take a peek
at recent libstdc++ commits where r261525 looks like it
introduced __glibcxx_check_can_increment_range, so it
seems like it might have something to
On 06/12/2018 03:26 PM, Martin Sebor wrote:
> Bootstrap fails in libstdc++ with the following error.
> I haven't investigated it much except to take a peek
> at recent libstdc++ commits where r261525 looks like it
> introduced __glibcxx_check_can_increment_range, so it
> seems like it might have so
Bootstrap fails in libstdc++ with the following error.
I haven't investigated it much except to take a peek
at recent libstdc++ commits where r261525 looks like it
introduced __glibcxx_check_can_increment_range, so it
seems like it might have something to do with it. I don't
see a __glibcxx_requi
On 06/12/2018 06:22 PM, Hrishikesh Kulkarni wrote:
Hi,
I tried tweaking the make file. I am probably missing something. Please advise.
Hi.
Next time please send diff. It's easier to read it. You'll need something like:
diff --git a/gcc/lto/config-lang.in b/gcc/lto/config-lang.in
index 7cb7a7
Hi,
I tried tweaking the make file. I am probably missing something. Please advise.
Regards,
Hrishikesh
On Mon, Jun 11, 2018 at 1:36 PM, Martin Liška wrote:
> On 06/08/2018 07:16 PM, Hrishikesh Kulkarni wrote:
>> Hi,
>>
>> -fdump-lto-body=foo
>> will dump gimple body of the function foo
>>
>>
On 12 June 2018 at 06:49, 刘超杰 wrote:
> Hi:
> When I was using g++, I found a problem, maybe which is a bug or not.
This is the wrong mailing list for your question. Please use the
gcc-h...@gcc.gnu.org list for help and questions about GCC.
> It is about the order of object files needed to link,
