> It was supposed to not change the set of conflicts, no. But I made a
> thinko, and sometimes too many conflicts are generated. On the testcases
> I tried that wasn't the case, so thanks for finding one :)
You're welcome. In fact, I should have installed it in the gnat.dg testsuite
long ago b
A mere two months after you posted the patch:
Jason Merrill writes:
> diff --git a/gcc/testsuite/g++.old-deja/g++.pt/ptrmem6.C
> b/gcc/testsuite/g++.old-deja/g++.pt/ptrmem6.C
> index 8802e98..19f1591 100644
> --- a/gcc/testsuite/g++.old-deja/g++.pt/ptrmem6.C
> +++ b/gcc/testsuite/g++.old-deja/g+
On 20 January 2012 11:23, Paolo Carlini wrote:
> Hi,
>
>> Here's a different, partial fix for PR 49204, changing the timed waiting
>> functions to return future_status, but not returning
>> future_status::deferred, as that requires the ABI change detailed above.
>> This doesn't change the library A
This is a regression present since the 4.5.x series at least. We generate
wrong code (infinite loop for the testcase) for the renaming of a volatile
packed array with an address clause.
Tested on i586-suse-linux, applied on the trunk, 4.6 and 4.5 branches.
2012-01-21 Eric Botcazou
Dear all,
I applied the attached patch as obvious after building and regtesting it
on x86-64-linux. (Rev. 183368.) I will backport it to 4.6. (It's a
4.6/4.7 regression.)
While this patch is obvious, my initial plan was to compare the class
container names (actual->ts.u.derived->name ==
fo
On 01/21/2012 06:02 AM, Richard Sandiford wrote:
Does this mean that the { target c++98 } lines are acceptable in C++11,
while the { xfail c++11 } lines are still errors in C++11, but aren't
detected?
Right.
The reason for asking is that the line:
g<(void (A::*)())&B::f>(); // { dg-erro
Alexandre Oliva writes:
> On Nov 25, 2011, Jakub Jelinek wrote:
>> The numbers I got with your patch (RTL checking) are below, seems
>> the cumulative numbers other than 100% are all bigger with patched stage2,
>> which means unfortunately debug info quality degradation.
>
> Not really. I found
> We then go and check if i1_feeds_into_i2 and that check relies on the
> LOG_LINKS being up-to-date. We find that i2 can be combined with i3
> *but* we've then gone and made a transformation that results in Y
> being used but miss out emitting the set of Y.
>
> The attached patch appears to fix th
I've committed the following patch after successful
build and regression testing and Tobias' approval
in private email.
2012-01-21 Tobias Burnus
Steven G. Kargl
PR fortran/50556
* symbol.c (check_conflict): namelist-group-name cannot have the SAVE
attribu
On Mon, 16 Jan 2012, Jakub Jelinek wrote:
> Ok.
I also updated the copyright year and whitespace for a different
#define and applied the patch below to trunk.
Thanks for the review (and patch)!
Gerald
* config/kfreebsd-gnu.h (GNU_USER_DYNAMIC_LINKERX32): New macro.
(GNU_USER_DY
El 21 de gener de 2012 20:36, Gerald Pfeifer ha escrit:
> On Mon, 16 Jan 2012, Jakub Jelinek wrote:
>> Ok.
>
> I also updated the copyright year and whitespace for a different
> #define and applied the patch below to trunk.
>
> Thanks for the review (and patch)!
Thanks to you!
Best regards
--
The problem with these two bug reports is that the cfgloop does not do
a good job for disambiguating some loops. This patch rewrites
find_subloop_latch_edge_by_ivs to be better. It is able to detect
much more loops and gets the ones which are referenced in PR 50971 and
PR 35629. It does make sur
This patch to the Go frontend changes the way that type aliases are
handled. This approach lets us use the same typename that the program
uses in error messages. This patch also changes the rune type to be an
alias for int32 rather than for int, matching the similar change in the
gc Go compiler.
PR libstdc++/50982
* testsuite/30_threads/*: Add powerpc-ibm-aix* to target selectors.
This adds powerpc-ibm-aix* to the dg target selectors in 30_threads.
As explained in http://gcc.gnu.org/ml/libstdc++/2012-01/msg00126.html
those tests won't run by default, but can be run using:
This patch to libgo makes the builtin print function match the gc
compiler's builtin print function exactly. This changes how float,
complex, and pointer types are printed. This is mainly for the benefit
of the testsuite, although consistency does not hurt. Bootstrapped and
ran Go testsuite on x
In Go pointers are automatically dereferenced when calling value
methods. However, the Go frontend was accidentally permitting a double
dereference when calling a method on a pointer value, which the language
does not permit. This patch fixes the problem. Bootstrapped and ran Go
testsuite on x86
This patch to the Go frontend avoids some compiler crashes on erroneous
code. Bootstrapped and ran Go testsuite on x86_64-unknown-linux-gnu.
Committed to mainline.
Ian
2012-01-21 Ian Lance Taylor
* go-gcc.cc (Gcc_backend::type_size): Check for error_mark_node.
(Gcc_backend::
On 01/20/2012 08:04 AM, Dominique Dhumieres wrote:
The following patch fixes the problem.
The test fails on *-apple-darwin*: pr51916.
TIA
Dominique
Dominique or Iain, may I ask you to test this patch on darwin? I have a
sporadic access to a darwin machine.
Bootstrapped and tested on x86_
On 01/20/2012 08:04 AM, Dominique Dhumieres wrote:
The following patch fixes the problem.
The test fails on *-apple-darwin*: pr51916.
TIA
Dominique
Dominique or Iain, may I ask you to test this patch on darwin? I have a
sporadic access to a darwin machine.
Bootstrapped and tested on x86_
Hello Everyone,
This patch is for the Cilkplus branch in the C++ compiler. This patch will
implement builtin functions for array notations.
Thanking You,
Yours Sincerely,
Balaji V. Iyer.
diff --git a/gcc/ChangeLog.cilk b/gcc/ChangeLog.cilk
index 8d65ca2..11eca8e 100644
--- a/gcc/ChangeLog.c
Ping.
Patch retested with 1/18/2012 sources.
On 1/1/2012 1:01 PM, Douglas Rupp wrote:
This is for 32bit, "C" language only.
Tested by cross and then cross-native from x86_64 Linux
--Doug
21 matches
Mail list logo
