On Mon, Dec 14, 2015 at 07:04:06AM +, Segher Boessenkool wrote:
> convert_move does not know how to zero-extend a constant integer to the
> target mode -- simply because it does not know the target mode.
That last "target" should be "source", of course.
Segher
convert_move does not know how to zero-extend a constant integer to the
target mode -- simply because it does not know the target mode. As a
result, 32-bit SImode with the high bit set would be effectively sign-
extended instead of zero-extended.
This patch fixes it. Is this okay for trunk? (bo
Markus Trippelsdorf writes:
> Many developers are still using __attribute__((optimize())) in
> production code, although it quite broken.
Wo reads documentation? @) If you want to discourage it better warn once
at runtime.
-Andi
> You can list me as your sponsor.
I've been wanting him to be a djgpp target/host maintainer for years
anyway, so +1 from me :-)
On 12/12/2015 09:40 AM, Andris Pavenis wrote:
On 12/11/2015 12:32 AM, Jeff Law wrote:
On 12/05/2015 10:25 AM, Andris Pavenis wrote:
Patch enables LTO support for DJGPP in top level configure.ac
Andris
2015-12-05 Andris Pavenis
* configure.ac: enable LTO for *-*-msdosdjgpp
OK once prereqs h
On 24/11/15 13:24, Tom de Vries wrote:
On 16/11/15 12:59, Tom de Vries wrote:
On 09/11/15 20:52, Tom de Vries wrote:
On 09/11/15 16:35, Tom de Vries wrote:
Hi,
this patch series for stage1 trunk adds support to:
- parallelize oacc kernels regions using parloops, and
- map the loops onto the o
On 11/12/15 14:00, Richard Biener wrote:
On Fri, 11 Dec 2015, Tom de Vries wrote:
On 13/11/15 12:39, Jakub Jelinek wrote:
We simply have some compiler internal interface between the caller and
callee of the outlined regions, each interface in between those has
its own structure type used to co
Every release I try to dig through some old bug reports and clear them
out of the system. This release is no different.
I'm a bit surprised I didn't tackle bz19201 in prior releases given that
Kazu had an almost correct patch attached to the BZ.
I suspect this could be generalized to more
'twas about to post a fix for an old m68k bug when I noticed the m68k
target tests weren't clean. Two minor issues.
First, 20090709-1.c. It's expecting a definition and two references to
a string in the constant pool. However, one reference to that string
was eliminated in favor of using
Many developers are still using __attribute__((optimize())) in
production code, although it quite broken.
* doc/extend.texi (Common Function Attributes) [optimize]:
Discourage use of the optimize attribute.
diff --git a/gcc/doc/extend.texi b/gcc/doc/extend.texi
index 883d9b334ab5
10 matches
Mail list logo
