Following in response to a report on PR46728. Committed as obvious.
2012-03-12 Bill Schmidt
PR tree-optimization/46728
* gcc.target/powerpc/pr46728-4.c: Skip for powerpc*-*-darwin*.
* gcc.target/powerpc/pr46728-5.c: Likewise.
* gcc.target/powerpc/pr46728-8.c:
Rainer Orth writes:
> libgo:
> * configure.ac (OSCFLAGS): Remove *-*-solaris2.8 handling.
> (libgo_cv_lib_makecontext_stack_top): Remove
> sparc*-*-solaris2.8* handling.
> * configure: Regenerate.
As with the Irix 5 changes, just send the libgo patches to me rather
Hi,
I handled this issue as outlined by Jakub in the audit trail. For the
purpose of the bogus div by zero warning just using
c_inhibit_evaluation_warnings appears to work fine.
Tested x86_64-linux.
Thanks,
Paolo.
///
/cp
2012-03-12 Paolo Carlini
PR c++/52299
"William J. Schmidt" writes:
> Index: gcc/testsuite/gcc.target/powerpc/pr46728-13.c
> ===
> --- gcc/testsuite/gcc.target/powerpc/pr46728-13.c (revision 185247)
> +++ gcc/testsuite/gcc.target/powerpc/pr46728-13.c (working copy
OK.
Jason
On Mar 12, 2012, at 10:44 AM, Rainer Orth wrote:
> Since even extended support for Solaris 8 ends by March 31st, this patch
> removes Solaris 8 support from mainline.
One of the nice things about gcc is that gcc usually still works, long after a
vendor has abandoned a machine. I rather like that
On 03/12/2012 01:41 PM, Joseph S. Myers wrote:
As a *target macro* it makes sense to remove it - reomve it from
defaults.h, make it purely internal to dwarf2out.c. But I think it makes
sense to have it inside dwarf2out.c
Agreed.
Jason
OK from my point of view, except...
Rainer Orth writes:
> * config/mips/mips.h (TARGET_GPWORD): Remove IRIX 6 N64 handling.
> (TARGET_IRIX6): Remove.
> (TARGET_CPU_CPP_BUILTINS): Remove IRIX 6 handling.
> Don't define LANGUAGE_C, _LANGUAGE_C for Objective-C.
...looking at
Rainer Orth writes:
>> +/* { dg-skip-if "" { powerpc*-*-darwin* } { "*" } { "" } } */
>
> Please omit defaults to dg-skip-if: { "*" } { "" } are unnecessary and
> make the directive harder to read.
Oh, I forgot: please indicate why you are skipping the test in the
comment field, like:
/* { dg-s
On Mon, Mar 12, 2012 at 9:50 AM, H.J. Lu wrote:
> On Mon, Mar 12, 2012 at 12:46 AM, Uros Bizjak wrote:
>> On Mon, Mar 12, 2012 at 12:26 AM, H.J. Lu wrote:
>>
>>> Pmode may be DImode for x32. This patch calls
>>> gen_tls_global_dynamic_64_ and gen_tls_local_dynamic_base_64_,
>>> depending on Pmo
Jason Merrill writes:
> On 03/12/2012 01:41 PM, Joseph S. Myers wrote:
>> As a *target macro* it makes sense to remove it - reomve it from
>> defaults.h, make it purely internal to dwarf2out.c. But I think it makes
>> sense to have it inside dwarf2out.c
>
> Agreed.
Fine with me. I've just been
> One of the nice things about gcc is that gcc usually still works,
> long after a vendor has abandoned a machine. I rather like that gcc
> will just work, unlike vendor software, which often says, please buy
> a new machine. One doesn't have to remove support in gcc for
> something, just because
Mike Stump writes:
> On Mar 12, 2012, at 10:44 AM, Rainer Orth wrote:
>> Since even extended support for Solaris 8 ends by March 31st, this patch
>> removes Solaris 8 support from mainline.
>
> One of the nice things about gcc is that gcc usually still works, long
> after a vendor has abandoned a
On Mar 10, 2012, at 3:25 PM, Jonathan Wakely wrote:
> On 7 March 2012 05:22, Terry Guo wrote:
>> Hello,
>>
>> Can anybody please review and approve the following simple patch? Thanks
>> very much.
>>
>> http://gcc.gnu.org/ml/libstdc++/2011-08/msg00063.html
Ok. Ok for the release branches as rel
ken...@vlsi1.ultra.nyu.edu (Richard Kenner) writes:
>> One of the nice things about gcc is that gcc usually still works,
>> long after a vendor has abandoned a machine. I rather like that gcc
>> will just work, unlike vendor software, which often says, please buy
>> a new machine. One doesn't ha
On Mon, Mar 12, 2012 at 7:37 PM, Mike Stump wrote:
> On Mar 12, 2012, at 10:44 AM, Rainer Orth wrote:
>> Since even extended support for Solaris 8 ends by March 31st, this patch
>> removes Solaris 8 support from mainline.
>
> One of the nice things about gcc is that gcc usually still works, long a
On 03/12/2012 02:45 PM, Rainer Orth wrote:
What about DWARF_INITIAL_LENGTH_SIZE? Keep it as a macro inside
dwarf2out.c, too?
Please.
Jason
Hi Diego
This patch adds arm-grtev2-linux-gnueabi.xfail for our 4.6 branch
so that we can track regressions. This just established the test
baseline. The failures need to be investigated.
-Doug
2012-03-12 Doug Kwan
* contrib/testsuite-management/arm-grtev2-
On Mar 12, 2012, at 11:48 AM, Rainer Orth wrote:
> But both for those and Solaris 8, the time has come where maintaining them is
> more
> trouble than it's worth,
The nice thing is, anyone that disagrees with you, will step forward. :-)
Notice, I didn't disagree with you... I was only railing
On 12/03/12 14:58 , Doug Kwan wrote:
2012-03-12 Doug Kwan
* contrib/testsuite-management/arm-grtev2-linux-gnueabi.xfail:
New file.
OK.
Diego.
On Mar 12, 2012, at 11:40 AM, Rainer Orth wrote:
> Oh, I forgot: please indicate why you are skipping the test in the
> comment field, like:
>
> /* { dg-skip-if "PR tree-optimization/46728" { powerpc*-*-darwin* } } */
"-mpowerpc-gpopt unsupported" is arguably a better comment, as one can see
thi
OK, will do. I just copied the style of some other test cases that
skipped darwin, assuming that was the preferred syntax.
Thanks,
Bill
On Mon, 2012-03-12 at 19:40 +0100, Rainer Orth wrote:
> Rainer Orth writes:
>
> >> +/* { dg-skip-if "" { powerpc*-*-darwin* } { "*" } { "" } } */
> >
> > Plea
"William J. Schmidt" writes:
> OK, will do. I just copied the style of some other test cases that
> skipped darwin, assuming that was the preferred syntax.
No problem, I'll probably make a pass over the whole testsuite to remove
that cruft to avoid misleading others.
Rainer
--
--
On Mar 12, 2012, at 11:59 AM, Diego Novillo wrote:
> On 12/03/12 14:58 , Doug Kwan wrote:
>
>> 2012-03-12 Doug Kwan
>>
>> * contrib/testsuite-management/arm-grtev2-linux-gnueabi.xfail:
>> New file.
>
> OK.
Hum, kinda makes be wish we had all the xfail files for the release branches
On Mon, 2012-03-12 at 20:15 +0100, Rainer Orth wrote:
> "William J. Schmidt" writes:
>
> > OK, will do. I just copied the style of some other test cases that
> > skipped darwin, assuming that was the preferred syntax.
>
> No problem, I'll probably make a pass over the whole testsuite to remove
On Mar 12, 2012, at 12:29 PM, William J. Schmidt wrote:
> Thanks, Rainer. Here's a revised patch. OK to commit?
Ok. Thanks.
On 03/12/12 10:44, Rainer Orth wrote:
fixincludes:
* inclhack.def (math_exception): Remove duplicate.
(solaris_cond_init): Remove.
(solaris_sys_va_list): Remove Solaris 8 support.
I think I probably hate those COND initializers more than any other
thing that gets
On 12/03/12 15:27 , Mike Stump wrote:
So, I guess the question is, is there a down side to doing that? I can imagine
a
if [ -r "$srcdir/contrib/testsuite-management/$target.xfail ]; then
$srcdir/contrib/testsuite-management/validate_failures.py bla
bla
fi
Ye
On Sun, Mar 11, 2012 at 10:24 PM, H.J. Lu wrote:
> Here is the patch which is equivalent to clearing MASK_TLS_DIRECT_SEG_REFS
> when Pmode != word_mode. We need to keep
>
> else if (Pmode == SImode)
> {
> /* Always generate
> movl %fs:0, %r
On Mon, Mar 12, 2012 at 7:42 PM, H.J. Lu wrote:
>> 2012-03-12 H.J. Lu
>>
>> * config/i386/i386.c (ix86_gen_tls_global_dynamic_64): New.
>> (ix86_gen_tls_local_dynamic_base_64): Likewise.
>> (ix86_option_override_internal): Set ix86_gen_tls_global_dynamic_64
>> and i
On 12 March 2012 17:03, Rainer Orth wrote:
> Continuing with the patches to remove obsolete ports, here's the IRIX
> 6.5 removal patch.
...
> * libstdc++-v3/doc/xml/manual/internals.xml still uses IRIX as an
> example. I've kept that part since I guess it's up the libstdc++
> maintainers to deci
On 12 March 2012 17:44, Rainer Orth wrote:
> Since even extended support for Solaris 8 ends by March 31st, this patch
> removes Solaris 8 support from mainline. Given that extended support
> for Solaris 9 lasts until October 2014, I guess that will remain in GCC
> for at least one major release.
> Thanks. That seems to get me into Ada bootstrap land together with
> the following two patches applied (but not when I apply only the
> first patch due to the stale TREE_OVERFLOW bits on type/decl sizes).
You're welcome. Let me give them a whirl...
--
Eric Botcazou
> "Rainer" == Rainer Orth writes:
Rainer> libjava:
Rainer> * configure.ac (THREADLIBS): Remove *-*-solaris2.8 handling.
Rainer> * configure: Regenerate.
This part is ok. Thanks.
Tom
> "Rainer" == Rainer Orth writes:
Rainer> libcpp:
Rainer> * lex.c: Remove Solaris 8 reference.
Also ok.
Tom
Add GCC support for -gfission option. Debug info is partitioned
into skeleton sections that will remain in the .o file, and "dwo"
sections that will be moved to a .dwo file. After compilation,
the gcc driver calls objcopy twice: once to extract the "dwo"
sections into the .dwo file, and a second
Hi,
On Mon, Mar 12, 2012 at 04:26:21PM +0100, Michael Matz wrote:
> Hi,
>
> On Mon, 12 Mar 2012, Martin Jambor wrote:
>
> > when we expand a misaligned MEM_REF on the LHS, we must not call the
> > code in expand_expr_real_1 if the subsequent patch is applied, because
> > the code generates code
On Mar 12, 2012, at 12:37 PM, Diego Novillo wrote:
> Ideally, though, we would not even need this hack. 'make check' should
> return 0 when every test is nominal. Period.
Yeah, that pig has yet to achieve lift-off. :-)
On Mon, 12 Mar 2012, Rainer Orth wrote:
> Tested with make doc/gccinstall.info doc/gccinstall.pdf, ok for mainline
> and 4.7 branch?
+Sun does not ship a C compiler with Solaris 2 before Solaris 10, though
+you can download the Sun Studio compilers for free. In Solaris 10 and
+11, GCC 3.4.3 is av
Hi,
currently when writing a value of type real or complex using
list-directed output, the G0 edit descriptor, or namelist output,
gfortran chooses the number of significant digits such that a
binary->ascii->binary roundtrip recovers the original value exactly,
per IEEE 754-2008. Assuming, of cour
[Revised patch to fix problem with ASM_FINAL_SPEC in the case where
neither -c nor -o are specified.]
Add GCC support for -gfission option. Debug info is partitioned
into skeleton sections that will remain in the .o file, and "dwo"
sections that will be moved to a .dwo file. After compilation,
t
On Mon, Mar 12, 2012 at 12:58 PM, Uros Bizjak wrote:
> On Mon, Mar 12, 2012 at 7:42 PM, H.J. Lu wrote:
>
>>> 2012-03-12 H.J. Lu
>>>
>>> * config/i386/i386.c (ix86_gen_tls_global_dynamic_64): New.
>>> (ix86_gen_tls_local_dynamic_base_64): Likewise.
>>> (ix86_option_override
On 2012/03/12 21:32:46, Cary wrote:
[Revised patch to fix problem with ASM_FINAL_SPEC in the case where
neither -c nor -o are specified.]
Add GCC support for -gfission option. Debug info is partitioned
into skeleton sections that will remain in the .o file, and "dwo"
sections that will be mov
> Thus, I suggest that the choice of d should be based on readability
> and usefulness for the common case rather than guaranteeing an exact
> roundtrip.
I'm not sure I see the value in this choice. In addition to standard
requirements, quality of implementation issues shouldn't be neglected. At
> * Although libgcc/config/sparc/sol2-unwind.h could be simplified quite a
> bit, perhaps we could go further: I wonder if the remaining nframes = 2
> case really applies to Solaris 9. If not, one could massivly simplify
> this code.
Please no, let's keep being very conservative with this s
On Mon, Mar 12, 2012 at 12:39 PM, Uros Bizjak wrote:
> On Sun, Mar 11, 2012 at 10:24 PM, H.J. Lu wrote:
>
>> Here is the patch which is equivalent to clearing MASK_TLS_DIRECT_SEG_REFS
>> when Pmode != word_mode. We need to keep
>>
>> else if (Pmode == SImode)
>> {
>>
Hi,
This sets MALLOC_ABI_ALIGNMENT to 64 bits on ARM which should be safe
on all AAPCS implementations given that this is a requirement on our
alignment specifiers. I would expect this to be true for most modern
malloc implementations on AAPCS targets -
Ok ?
Ramana
2012-03-12 Ramana Radhakris
On 12 March 2012 18:58, Doug Kwan wrote:
> Hi Diego
>
> This patch adds arm-grtev2-linux-gnueabi.xfail for our 4.6 branch
> so that we can track regressions. This just established the test
> baseline. The failures need to be investigated.
Just out of curiosity, were these w
Hi Ramana,
We know the limit of the QEMU and already noticed failure due to
the simulator. Like I said, this is used as the baseline. We are
going to look at the failures carefully to categorize them. We
noticed that some tests fail randomly on QEMU, these are marked as
flaky and the validat
This patch makes -fsized-delete define a macro __GXX_DELETE_WITH_SIZE__. If
this macro is defined, the deallocate function in new_allocator.h invokes
the two parameter delete operator with the size of the object. Tested by
bootstrapping the compiler and ensuring no tests are broken. Also verified
t
On Mon, Mar 12, 2012 at 8:03 PM, Easwaran Raman wrote:
>
> OK for google/main and google/4_6 branches?
You will need to check this into google/gcc-4_7 as well.
Ollie
On Mon, Mar 12, 2012 at 3:35 PM, H.J. Lu wrote:
> On Mon, Mar 12, 2012 at 12:39 PM, Uros Bizjak wrote:
>> On Sun, Mar 11, 2012 at 10:24 PM, H.J. Lu wrote:
>>
>>> Here is the patch which is equivalent to clearing MASK_TLS_DIRECT_SEG_REFS
>>> when Pmode != word_mode. We need to keep
>>>
>>>
ok. As Ollie said, it needs to be in google/gcc-4_7 as well.
David
On Mon, Mar 12, 2012 at 6:03 PM, Easwaran Raman wrote:
> This patch makes -fsized-delete define a macro __GXX_DELETE_WITH_SIZE__. If
> this macro is defined, the deallocate function in new_allocator.h invokes
> the two parameter
I forgot to commit headers, but that was fixed in an hour. At the
moment trunk builds
K
On Mon, Mar 12, 2012 at 6:36 PM, H.J. Lu wrote:
> On Sun, Mar 11, 2012 at 1:16 AM, Kirill Yukhin
> wrote:
>>>
>>> The patch is OK for mainline, if there are no further comments in next 24h.
>>
>> Thank you!
101 - 154 of 154 matches
Mail list logo
