Hello,
I would like to test a GCC patch on the platform it is supposed to
affect (PowerPC). In order to to this, I'm using the following
documentation:
https://gcc.gnu.org/simtest-howto.html
However, after fresh CVS checkouts (even without my changes on the GCC
tree) and the correspondi
On 08 Sep 2014, at 12:01, Pierre-Marie de Rodat wrote:
> Hello,
>
> I would like to test a GCC patch on the platform it is supposed to affect
> (PowerPC). In order to to this, I'm using the following documentation:
>
>https://gcc.gnu.org/simtest-howto.html
>
> However, after fresh CVS ch
How to identify object of a class which is defined in the library file?
For e.g.
struct basic_ostream & D.2782;
Variable D.2782 is object of class which is part of the library file.
How can we identify such a variable?
Regards,
Swati
On 8 September 2014 11:53, Swati Rathi wrote:
>
> How to identify object of a class which is defined in the library file?
>
> For e.g.
> struct basic_ostream & D.2782;
>
>
> Variable D.2782 is object of class which is part of the library file.
> How can we identify such a variable?
Repeating the
I am referring to C++ standard library files.
Statement : cout << "\tB:f" << endl;
is translated as :
struct basic_ostream & D.2782;
struct basic_ostream & D.2781;
:
D.2782_1 = operator<< (&cout, "\tB:f");
D.2781_2 = D.2782_1;
operator<< (D.2781_2, endl);
I want to ignore variables
On 09/08/2014 12:26 PM, Tristan Gingold wrote:
CVS ? Binutils (and gdb) are now using git:
Huh! I knew this, but not being a daily CVS user, I though the commands
in the documentation would get a binutils version that was somehow
tailored for GCC's needs. Anyway, here is what I just tried in
On 08 Sep 2014, at 16:51, Pierre-Marie de Rodat wrote:
> On 09/08/2014 12:26 PM, Tristan Gingold wrote:
>> CVS ? Binutils (and gdb) are now using git:
>
> Huh! I knew this, but not being a daily CVS user, I though the commands in
> the documentation would get a binutils version that was someh
Hi,
It appears that the current program point was not incremented when an early
clobber pseudo register was marked as dead.
The patch below solves the problem for both testcases. I'll post the patch
along with a testcase to gcc-patches mailing list after running
the regression on, at least, x8
Attached is an extended version of the patch, it brings a 100% improvement in
make -j32 -k check-gcc (down from 20min to <10min) by modification of
check_gcc_parallelize.
It includes one non-trivial part, namely a split of the target exps. They are
now all split using a common choice (based on
