wide-int fails to build libitm because of a bad interaction between:
/* Keep the OI and XI modes from confusing the compiler into thinking
that these modes could actually be used for computation. They are
only holders for vectors during data movement. */
#define MAX_BITSIZE_MODE_ANY_INT (1
On 04/16/2014 12:16 PM, Rainer Orth wrote:
> * I'm removing the check from classpath. Again, I'm
> uncertain if this is desirable. In the past, classpath changes were
> merged upstream by one of the libjava maintainers.
We should not diverge from GNU Classpath unless there is a strong reaso
On Thu, 17 Apr 2014 11:59:16 +
Zoran Jovanovic wrote:
> --- a/gcc/doc/invoke.texi
> +++ b/gcc/doc/invoke.texi
> @@ -7789,6 +7789,11 @@ pointer alignment information.
> This pass only operates on local scalar variables and is enabled by default
> at @option{-O} and higher. It requires that
Jeff Law writes:
> On 04/16/14 07:37, Jakub Jelinek wrote:
>>
>> Creating a (mem (scratch)) too early may pessimize code too much,
>> perhaps it can be used during say sched1 etc. for alias analysis, (mem
>> (scratch)) is considered to alias everything,.
>> Plus, I think at least so far we have no
I had sent this patch during stage-3 of gcc-4.9.
Is the patch OK ?
On Thu, Feb 20, 2014 at 6:26 PM, Marek Polacek wrote:
> On Thu, Feb 20, 2014 at 05:52:09PM +0530, Prathamesh Kulkarni wrote:
>> Show column number of left operand instead of comma operator
>> in the warning "left-hand operand of c
On Tue, Mar 11, 2014 at 8:00 PM, David Malcolm wrote:
> Investigation revealed the issue to be a CFG from the previous compile
> being kept alive by this GC root in gcse.c:
> static GTY(()) rtx test_insn;
>
> This wouldn't it itself be an issue, but one (or more) of the edges had:
But th
On 04/17/2014 12:00 PM, Marek Polacek wrote:
== CPP_CLOSE_PAREN)))
{
tree arg1 = c_parser_peek_token (parser)->value;
+ if (!attr_takes_id_p)
+ {
+ /* This is for enum values, so that they can be used as
+
On Sat, Apr 19, 2014 at 3:24 PM, Steven Bosscher wrote:
> On Tue, Mar 11, 2014 at 8:00 PM, David Malcolm wrote:
>> Investigation revealed the issue to be a CFG from the previous compile
>> being kept alive by this GC root in gcse.c:
>> static GTY(()) rtx test_insn;
>>
>> This wouldn't it
On 04/16/14 04:16, Rainer Orth wrote:
I've already verified that trunk fails to build no sparc-sun-solaris2.9
and i386-pc-solaris2.9. Bootstraps on {i386,sparc}-*-solaris2.{10,11}
(and x86_64-unknown-linux-gnu for good measure) are in progress. I'll
verify that there are no unexpected fixinclud
Patch 1 only quotes arguements where quotes are needed as otherwise the
32k limit can be hit sooner than otherwise. This patch should also be
applied to binutils.
Patch 2 makes path-exists semantics behave more like Posix in the face of
../ so that (for example) glibc can be cross compiled on Wind
We only quote arguments that contain spaces, \n \t \v
or " characters to prevent wasting 2 characters per
argument of the CreateProcess() 32,768 limit.
libiberty/
* pex-win32.c (argv_to_cmdline): Don't quote
args unnecessarily
---
libiberty/ChangeLog | 5 +
libiberty/pex-wi
Windows does a short-circuit lookup of paths containing
../ which means that:
exists/doesnotexist/../file
is considered to exist, while on Posix it is considered
not to. The Posix semantics are relied upon when building
glibc so any paths containing "../" are checked component
wise.
libcpp/
Hello Ray,
Patches to libiberty need to be cross-posted to binutils, gdb, and gcc ML. I
did so for you now.
- Original Message -
> We only quote arguments that contain spaces, \n \t \v
> or " characters to prevent wasting 2 characters per
> argument of the CreateProcess() 32,768 limit.
Hello Ray,
- Original Message -
> Windows does a short-circuit lookup of paths containing
> ../ which means that:
>
> exists/doesnotexist/../file
>
> is considered to exist, while on Posix it is considered
> not to. The Posix semantics are relied upon when building
> glibc so any paths c
> Date: Sat, 19 Apr 2014 16:23:33 -0400 (EDT)
> From: Kai Tietz
> Cc: gcc-patches@gcc.gnu.org, ktiet...@gmail.com,
> "binut...@sourceware.org Development" ,
> gdb-patc...@sourceware.org
>
> > + /* We only quote arguments that contain spaces, \n \t \v or "
> > characters
> >
>
> This removes RTL loop unswitching (see last years discussion about
> compile-time issues of that pass). RTL loop unswitching is
> enabled together with GIMPLE loop unswitching at -O3 and by
> -floop-unswitch. It's clearly the wrong place to do high-level
> loop transforms these days, and the
16 matches
Mail list logo
