After try the latest gcc again (execuse me, during these days, I have to
do another things), all things OK, the kernel can be started by QEMU,
all related issues are fixed by other members.
I shall start the make check with qemu again (it is about 12-13 days).
I guess, this thread is almost spam
> As described both in the PR and patch comments, this patch fixes PR62151 by
> setting right value to ELIM_I0/ELIM_I1 when distributing REG_DEAD notes from
> i0/i1. It is said that distribute_notes had caused many bugs in the past.
> I think it still has bug in it, as noted in the PR. This patch
On 15/04/14 23:19 +0200, Rüdiger Sonderfeld wrote:
This patch adds support for std::time_get::get and std::time_get::do_get
[locale.time.get]. Currently do_get is not virtual because this caused
segfault errors for me.
Hi Rüdiger, I'm trying to apply this patch and the tests don't work.
There
On 20/12/14 13:07 +, Jonathan Wakely wrote:
On 15/04/14 23:19 +0200, Rüdiger Sonderfeld wrote:
This patch adds support for std::time_get::get and std::time_get::do_get
[locale.time.get]. Currently do_get is not virtual because this caused
segfault errors for me.
Hi Rüdiger, I'm trying to
If rs6000_split_logical is asked to invert the second operand (but not
the first), it emits RTL that is just that; but canonical RTL has the
first arm inverted if only one, not the second. This patch fixes that.
With that in place, the bug in PR target/64358 is easily fixed. Do
that. Also chang
On Sat, Dec 20, 2014 at 10:18 AM, Segher Boessenkool
wrote:
> If rs6000_split_logical is asked to invert the second operand (but not
> the first), it emits RTL that is just that; but canonical RTL has the
> first arm inverted if only one, not the second. This patch fixes that.
>
> With that in pl
Dear all,
please find attached a patch fixing the PR60289 with my recent patch on
PR60255. Please understand, that for this patch to work correctly you need to
have my previous patch from
https://gcc.gnu.org/ml/fortran/2014-12/msg00092.html
applied already to your gfortran sources.
I am still c
Hi
Following a discussion on Reflector that has been reported to me,
people are complaining about management of the vector capacity in the
pedantic debug mode. Even if it is not crystal clear in the Standard
there seems to be a consensus that clear shouldn't impact it. So here is
a simple
On 12/20/14 02:09, Chen Gang wrote:
By the way, if this thread really has negative effect with other members,
please warn me, I should not notify it to mailing list again, and try my
best to finish it within myself.
I appreciate your enthusiasm and perseverance in pursuing this bug.
If the pro
This patch below allows ubsan to run when libstdc++ is built but not installed
(something which happens on darwin, in particular). This fixes all 658 ubsan
failures when run in this particular configuration.
OK to commit?
FX
2014-12-20 Francois-Xavier Coudert
* lib/ubsan-dg.exp: A
On 20/12/14 17:29 +0100, François Dumont wrote:
Hi
Following a discussion on Reflector that has been reported to me,
people are complaining about management of the vector capacity in the
pedantic debug mode. Even if it is not crystal clear in the Standard
there seems to be a consensus that
Hi
I plan to work on new debug diagnostics for which I would like to
display the type having a problem so this is a patch to add this kind of
parameter.
Moreover I dealt with demangling to move from this kind of diagnostic:
/home/fdt/dev/gcc/build/x86_64-unknown-linux-gnu/libstdc++-v
On 20/12/2014 19:09, Jonathan Wakely wrote:
There are also 2 tests that XPASS:
XPASS: experimental/string_view/element_access/char/2.cc execution test
XPASS: experimental/string_view/element_access/wchar_t/2.cc execution
test
Debug assertions has been commented about because not compatib
On 12/21/2014 12:31 AM, Michael Eager wrote:
> On 12/20/14 02:09, Chen Gang wrote:
>> By the way, if this thread really has negative effect with other members,
>> please warn me, I should not notify it to mailing list again, and try my
>> best to finish it within myself.
>
> I appreciate your enth
> First, bootstrap a native compiler from current trunk. Then, use that
> native compiler to build the cross compiler configured with
> --enable-werror-always. (--enable-werror-always is only expected to work
> when GCC is being built with the same version of GCC, as the compiler may
> not be -We
Ping.
On 24-Nov-14, at 7:38 PM, John David Anglin wrote:
On 15-Sep-14, at 5:40 AM, Richard Biener wrote:
Let's wait for other opinions.
We now have implementations of strtol and strtoll in libiberty. So,
it's better to use
these than atoll. As suggested by Jakub, the patch now falls bac
Someone suggested this and it seemed like a reasonable thing to verify
(pretty much) that only a specific version of a file should be fixed.
I used the BSD check sum, so there is a 1/65000 chance of a false positive.
Incorporating md5sum seemed over the top.
Index: fixincludes/ChangeLog
==
Markus pointed out that my patch for DR 1558 slowed down the compiler
significantly for building Chrome: comparing entries in the template
specialization hash table had to spend a lot of time figuring out if
types were specializations of alias templates with dependent template
arguments in orde
18 matches
Mail list logo
