Hello!
> 2011-07-11 Harsha Jagasia
>
> AMD bdver2 Enablement
> * config.gcc (i[34567]86-*-linux* | ...): Add bdver2.
> (case ${target}): Add bdver2.
> * config/i386/driver-i386.c (host_detect_local_cpu): Let
> -march=native recognize bdver2 processors.
> * co
Hallo Rainer!
On Fri, 08 Jul 2011 13:25:13 +0200, Rainer Orth
wrote:
> 2011-06-22 Rainer Orth
>
> gcc:
> * config/dfp-bit.c, config/dfp-bit.h: Move to ../libgcc.
> * config/t-dfprules: Move to ../libgcc/config.
Seems that you forgot to remove the files from gcc/config/.
On Mon, Jul 11, 2011 at 1:50 AM, Andreas Krebbel
wrote:
> Hi,
>
> with the changes in the IVopts pass from last year I see a reduced
> number of induction variables used for the first of the 3 hotloops in
> the 436.cactus benchmark:
>
> http://gcc.gnu.org/viewcvs?view=revision&revision=162653
>
>
hi folks.
i'm having a problem with GCC 4.5.3 on netbsd-m68k target. i've tracked
it down to this change from several years ago:
> 2007-02-06 Joseph Myers
>
> * expr.c (emit_push_insn): If STRICT_ALIGNMENT, copy to an
> unaligned stack slot via a suitably aligned slot.
the prob
On Mon, Jul 11, 2011 at 1:57 PM, Michael Zolotukhin
wrote:
> Sorry, for sending once again - forgot to attach the patch.
>
> On 11 July 2011 23:50, Michael Zolotukhin
> wrote:
>> The attached patch enables use of vector instructions in memmov/memset
>> expanding.
>>
>> New algorithm for move-mode
On Mon, 20 Jun 2011, Bernd Schmidt wrote:
> New patch below. Retested on i686 and bfin.
Yay, bikeshedding opportunity! :P
Can we call them "leading *repeated* sign bits"? (in docs and
comments) Calling them "redundant" makes you think the
representation is not two's complement but new and improv
Oops. Changlog entry should read:
2011-07-11 DeLesley Hutchins
* tree-threadsafe-analyze.c (tree-threadsafe-analyze.c)
Changed to force rewrite on MEM_REF
This patch fixes get_canonical_lock_expr so that it works on lock
expressions that involve a MEM_REF. Gimple code can use either
MEM_REF or INDIRECT_REF in many expressions, and the choice of which
to use is somewhat arbitrary. The canonical form of a lock expression
must rewrite all MEM_REFs to
> :-) Apple has one of these sorts of creatures. You can see the code
> in the Apple tree, marked by APPLE LOCAL {begin ,end ,}bitfield
> reversal. Your code looks much nicer than the Apple code, I hope it
> works as well.
Amusingly enough, the patch was based on an earlier patch I had lying
ar
Ping.
On Wed, Jul 6, 2011 at 2:20 PM, H.J. Lu wrote:
> PING.
>
> On Thu, Jun 30, 2011 at 1:47 PM, H.J. Lu wrote:
>> On Thu, Jun 30, 2011 at 12:02 PM, Richard Henderson wrote:
>>> On 06/30/2011 11:23 AM, H.J. Lu wrote:
+#ifdef REG_VALUE_IN_UNWIND_CONTEXT
+typedef _Unwind_Word _Unwind_C
Hello, gentle maintainer.
This is a message from the Translation Project robot.
A revised PO file for textual domain 'gcc' has been submitted
by the German team of translators. The file is available at:
http://translationproject.org/latest/gcc/de.po
(This file, 'gcc-4.6.1.de.po', has just
No functional changes. Just tidying calls to VEC_iterate.
Tested on x86_64. Committed to branch.
Diego.
* pph-streamer-in.c (pph_in_scope_chain): Replace VEC_iterate
loops with FOR_EACH_VEC_ELT.
(pph_read_file_contents): Likewise.
* pph-streamer-out.c (pph_out_
This patch adapts an idea from Gab that allow us to register alternate
addresses in the cache. The problem here is making sure that symbols
read from a PPH file reference the right bindings.
If a symbol is in the global namespace when compiling a header file,
its bindings will point to NAMESPACE
This patch changes the way we re-register symbols as they are read
from the PPH image. Instead of calling pushdecl...(), we merge the
global bindings from the PPH file (scope_chain->bindings) into the
global bindings of the current translation unit.
This fixes 3 name lookup failures in the test
On Jul 11, 2011, at 1:52 PM, DJ Delorie wrote:
> Finally getting around to writing this one. The idea is to have an
> attribute which determines how bitfields are allocated
:-) Apple has one of these sorts of creatures. You can see the code in the
Apple tree, marked by APPLE LOCAL {begin ,end
On C6X, we want to use the "ndfa" option to give the scheduler maximum
freedom when assigning units to instructions. After scheduling is
complete, we process the insns again in c6x_reorg, looking at each cycle
and assigning a unit specifier to each instruction so that there is no
conflict within a
Note that this doesn't allow capture of a pack expansion yet, just fixes
a hole in the patch for c++/48424. When instantiating a template
function that has a non-pack parameter after a parameter pack, we were
incorrectly treating it as part of the pack, leading to confusion.
Tested x86_64-pc-
Resending in plain text:
On 11 July 2011 23:50, Michael Zolotukhin
wrote:
>
> The attached patch enables use of vector instructions in memmov/memset
> expanding.
>
> New algorithm for move-mode selection is implemented for move_by_pieces,
> store_by_pieces.
> x86-specific ix86_expand_movmem and
Finally getting around to writing this one. The idea is to have an
attribute which determines how bitfields are allocated within words
(lsb-first vs msb-first), assuming the programmer doesn't ask us to do
something impossible. __attribute__((bitorder(FOO))) where FOO is:
native (or omitted,
This patch to libgo defines CC_FOR_BUILD in Makefile, to make it more
likely to be able to build code in the libgo subdirectory. Bootstrapped
on x86_64-unknown-linux-gnu. Committed to mainline.
Ian
diff -r 4732400182b5 libgo/configure.ac
--- a/libgo/configure.ac Mon Jul 11 13:13:33 2011 -0700
+
On 07/11/2011 05:18 PM, Romain Geissler wrote:
> This patch add a new exception to the plugin header flattering strategy.
> c-family files can't be installed in the plugin include root directory as some
> other files like cp/cp-tree.h will look for them in the c-family directory.
>
> Furthermore,
Hi!
The final standard dropped const qualified vars without mutable member
back to being predetermined shared, but allows them to be specified in
firstprivate clause (so that valid OpenMP 3.0 using default(none)
aren't suddenly invalid).
The following patch implements that. I'm not 100% sure abou
This patch changes std::abort() to abort() in C code. I'm not sure how
this was working previously. Bootstrapped on x86_64-unknown-linux-gnu.
Committed to mainline.
Ian
diff -r 3291a9609c87 libgo/runtime/go-unwind.c
--- a/libgo/runtime/go-unwind.c Thu Jul 07 09:48:11 2011 -0700
+++ b/libgo/runt
Sometimes we compare cfa.reg with REGNO, and sometimes with
something that has been passed through DWARF_FRAME_REGNUM.
This leads to all sorts of confusion.
I think that ideally we'd leave dw_cfa_location.reg in the
GCC regno space, because that's convenient for the majority
of the code that inter
This is an updated version of Laurent's patch originally here:
http://gcc.gnu.org/ml/gcc/2009-06/msg00635.html
Bootstrapped/regtested on x86_64-suse-linux with --enable-build-with-cxx.
Arno, I think we should apply it. This isn't very intrusive in the end and
with it we can go full C++ instea
The PR complained about G++ getting into an infinite loop, but it isn't
really infinite; the problem is that in the testcase a function template
has an error and then depends on another instance of itself.
I've fixed this for many cases by refusing to instantiate a declaration
if there have be
Hi,
for details, see the audit trail. Compared to the last draft, I also
fixed __rotate_adaptive (issue noticed by artificially reducing the size
of the buffer).
Tested x86_64-linux, committed.
Thanks,
Paolo.
/
2011-07-11 Paolo Carlini
PR libstdc++/49559
Hi,
This patch does the basic enablement for AMD's upcoming bdver2 processor.
It defines -march=bdver2 and -mtune=bdver2, and lets -march=native correctly
recognizes bdver2. At the moment the tuning is mostly a copy of bdver1.
The patch passed bootstrap and the x86 tests.
Is it OK to commit to tr
Backported fix for PR46779 to 4.6:
http://gcc.gnu.org/viewcvs?root=gcc&view=rev&rev=176055
On Mon, Jul 11, 2011 at 08:26:22PM +0200, Tobias Burnus wrote:
> The attached patch updates the version number in gfortran's
> intrinsic documentation. I don't know whether it makes sense to keep
> the number, but if one does, it should be up to date.
>
> Jakub, is the attached patch OK for the br
The attached patch updates the version number in gfortran's intrinsic
documentation. I don't know whether it makes sense to keep the number,
but if one does, it should be up to date.
Jakub, is the attached patch OK for the branch?
Tobias
2011-07-11 Tobias Burnus
* intrinsic.c (OMP_LIB): U
**This patch goes on top of patches in issues 4672055 and 4675069 (which have
yet to be committed)**
Some things are built as soon as a tree is streamed in, and since the chains
are backwards, flipping them after streaming them in is not sufficient as some
things (e.g. unique numbers given to f
Hello,
This is my largest patch so far and the first that I'll commit myself.
This patch improves support for the ALLOCATE statement when using the
coarray library. Specifically, it adds support for the stat= and errmsg=
attributes:
ALLOCATE( x(n)[*] , stat=i , errmsg=str )
These attributes
Hello!
A small cleanup, no functional change. This allows us to assert that
generated code length is less than TRAMPOLINE_SIZE also for 32bit
targets.
2011-07-11 Uros Bizjak
* config/i386/i386.c (ix86_trampoline_init): Switch arms of if expr.
Use offset everywhere. Always as
On 07/11/2011 10:26 AM, Rainer Orth wrote:
> There's one other question here: alpha/t-crtfm uses
> -frandom-seed=gcc-crtfastmath with this comment:
>
> # FIXME drow/20061228 - I have preserved this -frandom-seed option
> # while migrating this rule from the GCC directory, but I do not
> # know why
Ping?
http://gcc.gnu.org/ml/gcc-patches/2011-06/msg01368.html
We had a bug report from a customer that the linker was ignoring the
--demangle and --no-demangle options when generating map files.
Moreover, it was failing in a host-dependent way; on Windows hosts,
it was always emitting demangled
Hi!
OpenMP 3.1 has been released on Saturday, this patch adjusts the
macros/parameters for that on gomp-3_1-branch. Apparently #pragma omp
atomic changed substantially from the draft and const vars are again
predetermined shared, but newly allowed in firstprivate. Will adjust
the branch for that
Backported to 4.6:
http://gcc.gnu.org/viewcvs?view=revision&revision=176143
On 07/11/2011 09:33 AM, Jakub Jelinek wrote:
> PR debug/49676
> * dwarf2out.c (int_shift_loc_descriptor): New function.
> (int_loc_descriptor): If shorter, emit i as
> (i >> shift), shift, DW_OP_shl for suitable shift value.
> Similarly, try to optimize large negative
Another low-hanging fruit in the toplevel libgcc move is crtfastmath.
The following patch moves the various crtfastmath.c files over to libgcc
and removes the remnants of the gcc side of the configuration.
Unfortunately, one piece needs to stay behind: crtfastmath.o must remain
in gcc/config/i386
Hi,
tested x86_64-linux, committed.
Paolo.
/
2011-07-11 Paolo Carlini
* testsuite/util/testsuite_allocator.h (propagating_allocator<>::
operator=(const propagating_allocator<>&)): Retun *this.
Index: testsuite/util/testsuite_allocator.h
==
On Mon, Jul 11, 2011 at 9:55 AM, H.J. Lu wrote:
> On Mon, Jul 11, 2011 at 8:54 AM, H.J. Lu wrote:
>> On Mon, Jul 11, 2011 at 4:03 AM, Paolo Bonzini wrote:
>>> On 07/11/2011 02:04 AM, H.J. Lu wrote:
With my original change, I got
(const:DI (plus:DI (symbol_ref:DI ("iplane.157
Hi,
I have just committed the following to the 4.6 branch (after
re-testing and as the rev. 176166) to fix PR 49094 there too. It's
the following two patches which are already in trunk in one:
http://gcc.gnu.org/ml/gcc-patches/2011-06/msg02342.html and
http://gcc.gnu.org/ml/gcc-patches/2011-06/m
Hi!
While working on the last dwarf2out.c patch, I've noticed we can generate
more compact DWARF location descriptions in several cases, e.g.
DW_OP_constu 0xf8000
is 7 byts long, while
DW_OP_lit31 DW_OP_lit31 DW_OP_shl
pushes the same value to the stack and is just 3 bytes long.
The patch adju
On 07/07/11 10:58, Richard Guenther wrote:
I think you should assume that series of widenings, (int)(short)char_variable
are already combined. Thus I believe you only need to consider a single
conversion in valid_types_for_madd_p.
Ok, here's my new patch.
This version only allows one conversi
On Mon, Jul 11, 2011 at 8:54 AM, H.J. Lu wrote:
> On Mon, Jul 11, 2011 at 4:03 AM, Paolo Bonzini wrote:
>> On 07/11/2011 02:04 AM, H.J. Lu wrote:
>>>
>>> With my original change, I got
>>>
>>> (const:DI (plus:DI (symbol_ref:DI ("iplane.1577") [flags 0x2]
>>> )
>>> (const_int -4 [0xff
When testing libmudflap on Solaris 8, 9, and 10 with GNU ld, I found a
couple of testsuite failures:
* On Solaris 10, several libmudflap.cth tests fail with
FAIL: libmudflap.cth/pass37-frag.c (test for excess errors)
Excess errors:
/vol/gcc/src/hg/trunk/local/libmudflap/testsuite/libmudflap.cth/p
I noticed that libgcc/configure.ac uses the gcc copy of i386/t-crtstuff
on Solaris/x86, while the identical libgcc copy is perfectly fine. This
patch corrects this.
Bootstrapped without regressions on i386-pc-solaris2.11, installed on
mainline.
Rainer
2011-07-10 Rainer Orth
While investigating why many libmudflap execution tests failed on
Solaris 11/x86 with Sun ld, but succeeded on Solaris 11/SPARC, I came
across the following:
The first failure is fail17-frag. With MUDFLAP_OPTIONS=-trace-calls, I see
mf: __mfwrap_strcpy
mf: check ptr=8050f8c b=995 size=10 read lo
On 07/11/2011 06:24 PM, Jakub Jelinek wrote:
As the attached testcase (on x86-64) shows, inner_size is initialized to
1 of a wrong type, which results in verify_stmt ICEs because a PLUS has
one 64-bit and one 32-bit operand.
Fixed thusly, bootstrapped/regtested on x86_64-linux and i686-linux.
Ok
Hi!
As the attached testcase (on x86-64) shows, inner_size is initialized to
1 of a wrong type, which results in verify_stmt ICEs because a PLUS has
one 64-bit and one 32-bit operand.
Fixed thusly, bootstrapped/regtested on x86_64-linux and i686-linux.
Ok for trunk/4.6?
2011-07-11 Jakub Jelinek
On a multicore ARM, you really do have to clear both caches, not just the
dcache. This bug may exist in other ports too.
Andrew.
2011-07-11 Andrew Haley
* src/arm/ffi.c (FFI_INIT_TRAMPOLINE): Clear icache.
diff --git a/src/arm/ffi.c b/src/arm/ffi.c
index 885a9cb..b2e7667 100644
---
On Mon, 11 Jul 2011, Mike Stump wrote:
> My take, you need approval for everything outside your area, once you
> have that, and that work is checked in, then, you can check in all the
> target bits, self approving those bits, if they meet your standard.
That's my understanding as well. (With
After installing the libgcov move patch, I noticed that I had overlooked
in instance in gcc/po/EXCLUDES.
This patch removes is, installed as obvious.
Rainer
2011-07-09 Rainer Orth
* EXCLUDES (libgcov.c): Remove.
diff --git a/gcc/po/EXCLUDES b/gcc/po/EXCLUDES
--- a/gcc/po/EX
> Hi,
>
> cgraph_get_node_or_alias is now completely equivalent to
> cgraph_get_node, in fact it is exactly same character-by-character.
> Therefore it should be removed, which is what the patch below does.
>
> Bootstrapped and tested on x86_64-linux, OK for trunk?
OK,
thanks!
Honza
Hi,
cgraph_get_node_or_alias is now completely equivalent to
cgraph_get_node, in fact it is exactly same character-by-character.
Therefore it should be removed, which is what the patch below does.
Bootstrapped and tested on x86_64-linux, OK for trunk?
Thanks,
Martin
2011-07-11 Martin Jambor
On Jul 11, 2011, at 3:18 AM, Bernd Schmidt wrote:
> On 06/06/11 14:53, Gerald Pfeifer wrote:
>> not a direct approval for any of the outstanding patches, but I am happy
>> to report that the steering committee is appointing you maintainer of the
>> C6X port.
>>
>> Please go ahead and add yourse
On Mon, Jul 11, 2011 at 4:03 AM, Paolo Bonzini wrote:
> On 07/11/2011 02:04 AM, H.J. Lu wrote:
>>
>> With my original change, I got
>>
>> (const:DI (plus:DI (symbol_ref:DI ("iplane.1577") [flags 0x2]
>> )
>> (const_int -4 [0xfffc])))
>>
>> I think it is safe to permute the con
2011/7/8 Richard Guenther :
> On Fri, Jul 8, 2011 at 1:32 PM, Kai Tietz wrote:
>> 2011/7/8 Richard Guenther :
>>> On Thu, Jul 7, 2011 at 6:07 PM, Kai Tietz wrote:
Hello,
This patch - second of series - adds boolification of comparisions in
gimplifier. For this
casts from
Mike Stump wrote:
> On Jul 8, 2011, at 7:57 AM, Georg-Johann Lay wrote:
>> These tests are too big for AVR: .text (128 KiB) overflows and ld
>> complains.
>>
>> Ok to commit?
>
> Ok. If people feel they have a nice design for `too big', let us
> know... I think it would have to be ld message s
This patch add a new exception to the plugin header flattering strategy.
c-family files can't be installed in the plugin include root directory as some
other files like cp/cp-tree.h will look for them in the c-family directory.
Furthermore, i had to correct an include in c-pretty-print.h so that i
On Thu, Jul 7, 2011 at 4:19 PM, Richard Guenther
wrote:
> Does XLC have a similar switch whose name we can use?
The IBM XL compiler is discussing a similar feature, but it is not
implemented yet and does not have a formal command line option name.
- David
On Sun, Jul 10, 2011 at 11:15 PM, Richard Henderson wrote:
>> + reload_completed = 1;
>> + epilogue_completed = 1;
>>
>> Do we really need these? Perhaps a comment should be added here, it is
>> not obvious at the first sight...
>
> We didn't need these. ia64 did because there we run a split p
Hi,
On Mon, 11 Jul 2011, Richard Guenther wrote:
> The following actually works.
>
> Bootstrapped and tested on x86_64-unknown-linux-gnu.
>
> Can you double-check it?
Seems sensible. Given this:
short s;
int i;
for (s = 0; s <= 127; s++)
i += (signed char)(unsigned char)s;
return
Hello,
As my very first commit to GCC I have added my name to the MAINTAINERS
file in the "Write After Approval" section.
--
I'm not overweight, I'm undertall.
Index: MAINTAINERS
===
--- MAINTAINERS (revision 176151)
+++ MAINTAINE
While working on another patch, I noticed that the new misaligned
load/store patterns allow REG+CONST addresses before reload, even though
the instruction (and its constraints) don't.
This patch tightens the predicatese to match the existing vstN patterns.
It depends on:
http://gcc.gnu.org/ml/g
On Fri, 8 Jul 2011, Richard Guenther wrote:
> On Fri, 8 Jul 2011, Michael Matz wrote:
>
> > Hi,
> >
> > On Fri, 8 Jul 2011, Richard Guenther wrote:
> >
> > > It should be indeed safe with the current handling of conversions, but
> > > better be safe. So, like the following?
> >
> > No. The
This is the first patch in a series of patches that will eventually lead
to changed requirements for the POINTER_PLUS_EXPR offset operand. The
first and foremost goal is to reduce the number of sizetyped computations
in our IL (with sizetype being that oddball type that is unsigned
but sign-exten
On 03/25/2009 04:30 PM, Andreas Krebbel wrote:
>> 2009-03-23 Arthur Loiret
>>
>> * config.gcc (s390-*-linux*): If 'enabled_targets' is 'all', build
>> a bi-arch compiler defaulting to 31-bit. In this case:
>> (tmake_file): Add s390/t-linux64.
>> * doc/install.texi: Add s390-l
On 06/25/2009 11:23 AM, Arthur Loiret wrote:
> Hello,
>
> 2009/6/24, Matthias Klose :
>> Richard Sandiford schrieb:
>>> Thanks for the update.
>>>
>>> This patch didn't go in at the time because Arthur's copyright
>>> assignment went astray somewhere. Arthur, do you know if
>>> everything's sorte
On 07/11/11 13:08, Richard Sandiford wrote:
> Bernd Schmidt writes:
>> On 07/07/11 22:08, Richard Sandiford wrote:
>>> Sure, I understand that returns does more than return on ARM.
>>> What I meant was: we'd normally want that other stuff to be
>>> expressed in rtl alongside the (return) rtx. E.g
Bernd Schmidt writes:
> On 07/07/11 22:08, Richard Sandiford wrote:
>> Sure, I understand that returns does more than return on ARM.
>> What I meant was: we'd normally want that other stuff to be
>> expressed in rtl alongside the (return) rtx. E.g. something like:
>>
>> (parallel
>> [(retu
On Mon, Jul 11, 2011 at 12:38 PM, Richard Sandiford
wrote:
> When I added the new optabs insn-expansion routines, I looked for code
> that checked the predicates before calling GEN_FCN. This patch also
> uses the routines in two cases where we don't currently check the
> predicates. The benefits
On 07/11/2011 02:04 AM, H.J. Lu wrote:
With my original change, I got
(const:DI (plus:DI (symbol_ref:DI ("iplane.1577") [flags 0x2]
)
(const_int -4 [0xfffc])))
I think it is safe to permute the conversion and addition operation
if one operand is a constant and we are zero-
When I added the new optabs insn-expansion routines, I looked for code
that checked the predicates before calling GEN_FCN. This patch also
uses the routines in two cases where we don't currently check the
predicates. The benefits are:
1) We assert that the predicates really do match.
2) We supp
On 06/06/11 14:53, Gerald Pfeifer wrote:
> not a direct approval for any of the outstanding patches, but I am happy
> to report that the steering committee is appointing you maintainer of the
> C6X port.
>
> Please go ahead and add yourself to the MAINTAINERS file as part of the
> patch that act
On 07/06/11 20:37, Richard Henderson wrote:
> On 07/01/2011 10:42 AM, Bernd Schmidt wrote:
>> get_mode_bounds should also use GET_MODE_PRECISION, but this exposes a
>> problem on ia64 - BImode needs to be handled specially here to work
>> around another preexisting special case in gen_int_mode.
>
On Mon, Jul 11, 2011 at 10:50 AM, Andreas Krebbel
wrote:
> Hi,
>
> with the changes in the IVopts pass from last year I see a reduced
> number of induction variables used for the first of the 3 hotloops in
> the 436.cactus benchmark:
>
> http://gcc.gnu.org/viewcvs?view=revision&revision=162653
>
>
On Mon, Jul 11, 2011 at 9:53 AM, Romain Geissler
wrote:
> 2011/7/8 Richard Guenther :
>> Ok.
>>
>> Thanks,
>> Richard.
>>
>
> Hi,
>
> I don't have write access, can you please add the patch to the trunk ?
Done. Btw, a proper changelog would have been
2011-07-11 Romain Geissler
* tree
Hi,
since (same body) aliases have their own cgraph_nodes, the check for
them in cgraph_redirect_edge_call_stmt_to_callee is now unnecessary
because e->callee is now the alias, not the function node.
The following patch therefore removes it. Bootstrapped and tested on
x86_64-linux, OK for trunk?
2011/7/11 Georg-Johann Lay :
> char >> 7 is compiled to
>
> LSL reg
> SBC reg,reg
>
> which leaves cc0 in a mess because Z-flag is not set by SBC, it's
> propagated from LSL.
>
> Patch as obvious, new testcase pass and contains *cmpqi.
>
> Ok to commit?
>
Please, commit.
Denis.
On Fri, Jul 8, 2011 at 7:25 PM, Jeff Law wrote:
> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA1
>
>
> As detailed in the PR, improvements to jump threading caused the
> relatively simple guard predicates in this testcase to become
> significantly more complex. The predicate complexity is enough
Since DWARF2 uses DW_CFA_GNU_window_save and the middle-end REG_CFA_WINDOW_SAVE
to designate the thing, this makes the SPARC back-end use the same wording.
Tested on SPARC/Solaris, applied on the mainline.
2011-07-11 Eric Botcazou
* config/sparc/sparc.md (save_register_window_1): Re
I work on target with complex mode switching needs, so it can happen that
in some block, for an entity a mode is provided without the need for a set.
This causes the current optimize_mode_switching to crash when it later
dereferences a NULL seginfo pointer.
Fixed by using an actual flag to keep tr
Hi,
with the changes in the IVopts pass from last year I see a reduced
number of induction variables used for the first of the 3 hotloops in
the 436.cactus benchmark:
http://gcc.gnu.org/viewcvs?view=revision&revision=162653
Which leads to an heavily increased number of instructions in the body
o
char >> 7 is compiled to
LSL reg
SBC reg,reg
which leaves cc0 in a mess because Z-flag is not set by SBC, it's
propagated from LSL.
Patch as obvious, new testcase pass and contains *cmpqi.
Ok to commit?
Johann
gcc/
PR target/39633
* config/avr/avr.c (notice_update_cc): For as
Hi all,
when committing the LOCK patch, I forgot to include attached change in
the testsuite, which causes testsuite failures.
I planned to correct that together with other constraint-check issues,
but obviously I haven't done so for several weeks. Thus, I decided to
start by fixing the test
2011/7/8 Richard Guenther :
> Ok.
>
> Thanks,
> Richard.
>
Hi,
I don't have write access, can you please add the patch to the trunk ?
Romain Geissler
2011/7/7 Diego Novillo :
> OK. This one fell through the cracks in my inbox. Apologies.
>
>
> Diego.
Hi,
I don't have write access, can you please add the patch to the trunk ?
Romain Geissler
On 07/10/2011 09:56 PM, Tobias Burnus wrote:
This patch implemented the trans*.c part of allocatable scalar
coarrays; contrary to noncoarray allocatable scalars, they have
cobounds and thus use an array descriptor.
I found a test case (part of Reinhold Bader's fortran_tests), which gave
an IC
2011/7/6 Romain Geissler :
>
> I forgot configure was a generated script. Here is the patch that fix
> it at the m4 macro level :
>
>
> 2011-07-06 Romain Geissler
>
> * config/cloog.m4: Add $gmplibs to cloog $LDFLAGS
> * configure: Regenerate
>
>
> Index: config/cloog.m4
>
91 matches
Mail list logo
