On Nov 3, 2015, at 1:10 PM, Martin Sebor wrote:
> The "as if" requirement implies that any observable effects of
> "the (possibly replaced) ordinary version" must be preserved.
> The repeated calls to the new handler are among such effects.
Unless the standard is fixed to say
On Nov 3, 2015, at 2:17 PM, Michael Meissner
wrote:
> The intention was to keep those to allow other compilers (XL, LLVM) to use
> these functions for developing their own IEEE 128-bit support. However, since
> I posted the patch, those groups feel they cannot use
On Nov 2, 2015, at 8:29 AM, Richard Sandiford wrote:
> switch (GET_CODE (rtl))
> {
> case CONST_INT:
> - {
> - HOST_WIDE_INT val = INTVAL (rtl);
> + if (mode != BLKmode)
This changes BLKmode for CONST_INT, but I didn’t see this discussed. I
On Nov 2, 2015, at 12:55 PM, Richard Sandiford
wrote:
> This was:
>
> ... Sometimes structure decls
> have BLKmode but are assigned an integer-mode rtl (e.g. when passing
> 3-byte structures by value to functions).
> [...]
> loc_descriptor refuses to use
On Oct 30, 2015, at 1:56 AM, Eric Botcazou wrote:
>> It won’t. Fixing the language line for the options and a make to ensure it
>> still builds for you is enough testing.
>
> I was talking about the feature itself though, not about the option per se.
> The feature is
On Oct 29, 2015, at 10:39 PM, Andi Kleen wrote:
> David Malcolm writes:
>>
>> * adds -Wmisleading-indentation to -Wall
>
> I have doubts this is a good idea. I'm sure this will break
> a bazillion packages which (misguidedly) ship with -Wall -Werror.
On Oct 30, 2015, at 4:48 AM, tbsaunde+...@tbsaunde.org wrote:
> Its not the nicest code in the world, and there's definitely room for
> cleanups,
> however it seems like an improvement. After this series the only usage of
> tm.h
> in libobjc is thr.c which only uses tm.h so it can include
On Oct 30, 2015, at 9:20 AM, Andrew MacLeod <amacl...@redhat.com> wrote:
> On 10/30/2015 12:07 PM, Mike Stump wrote:
>> On Oct 30, 2015, at 6:37 AM, Andrew MacLeod <amacl...@redhat.com> wrote:
>>> OK, here's the much delayed front end reduction patch based on the
On Oct 30, 2015, at 6:37 AM, Andrew MacLeod wrote:
> OK, here's the much delayed front end reduction patch based on the reordering
> already being checked in.
So, Objective-C++ should be toggled on at least once for this. If it builds,
it should be fine; though the entire
On Oct 29, 2015, at 10:56 AM, Patrick Palka <patr...@parcs.ath.cx> wrote:
> On Thu, Oct 29, 2015 at 1:50 PM, Mike Stump <mikest...@comcast.net> wrote:
>> On Oct 29, 2015, at 10:42 AM, Patrick Palka <patr...@parcs.ath.cx> wrote:
>>> However we should defin
On Oct 29, 2015, at 10:42 AM, Patrick Palka wrote:
> However we should definitely not warn on
>
>if (foo)
> bar ();
>
> {
>baz ();
> }
>
> Since that is valid GNU-style code :)
I’ll put it differently; no, that formatting is wrong.
On Oct 29, 2015, at 12:32 PM, Jeff Law wrote:
> Something similar for RTL would be cool, but probably even harder given the
> amount of state that's traditionally been kept out of the IL stream. I'm
> sure some things are better today than in the past, but it's probably a very
On Oct 27, 2015, at 12:48 PM, David Malcolm wrote:
> The following patch kit adds a unit tests framework for gcc,
I’m supportive of the patch set and the concept in general. I don’t know who
wants to review this, Jeff seems on track to do this. My only guidance would
be
On Oct 28, 2015, at 3:04 PM, Eric Botcazou wrote:
>> Why is -fsso-struct= listed only for C and C++, not ObjC and ObjC++?
>
> Because it was not tested with the latter 2 languages at all and may require
> specific adjustments in the respective front-ends to work.
It
On Oct 23, 2015, at 10:24 AM, Bernd Schmidt <bschm...@redhat.com> wrote:
> On 10/23/2015 07:15 PM, Mike Stump wrote:
>> On Oct 23, 2015, at 9:57 AM, Bernd Schmidt <bschm...@redhat.com>
>> wrote:
>>>
>>> I'm guessing it's the CROSS_DIRECTORY_STRUCT
On Oct 23, 2015, at 9:57 AM, Bernd Schmidt wrote:
>
> I'm guessing it's the CROSS_DIRECTORY_STRUCTURE macro which is used by darwin
> targets. It's also used for several other targets, so you may want to double
> check those.
No, only darwin is special, as presently only
On Oct 23, 2015, at 10:36 AM, Andrew MacLeod wrote:
>
> darwin-driver.c had some code that depended on one of the include files, bit
> no other part of the file needed it, so that was the issue there. The only
> other place it seems could be an issue is with collect2.c...
On Oct 19, 2015, at 12:46 PM, H.J. Lu wrote:
Ok. Does this need to go into the gcc-5 release branch as well? If so, ok
there too. Thanks.
>>> I think there is no need for it.
>>
>> It is also need for gcc-5. I am backporting it now.
>
> This is what I checked
On Oct 20, 2015, at 3:55 PM, Bernd Schmidt wrote:
> On 10/16/2015 10:21 PM, Steve Ellcey wrote:
>> Here is the second part of the MIPS frame header optimization patch.
>
> I'll leave reviewing the functionality to the MIPS maintainers. But...
>
>> + return
On Oct 21, 2015, at 8:01 AM, Jakub Jelinek wrote:
> On Wed, Oct 21, 2015 at 05:56:42PM +0300, Maxim Ostapenko wrote:
>>
>> recent libsanitizer merge (
>> https://gcc.gnu.org/ml/gcc-patches/2015-10/msg01851.html) broke bootstrap on
>> x86_64-apple-darwin14 because for Darwin
On Oct 18, 2015, at 3:42 AM, Iain Sandoe wrote:
This seems likely to break cross-compilers to Darwin that do not have
the system libraries available. I guess I don't care about that if
you don't.
>>>
>>> I do care about it, but I'm not visualising the
On Aug 5, 2015, at 7:14 AM, Richard Sandiford wrote:
> wi::from_mpz reads the absolute value of the mpz and then negates the
> result if the mpz is negative. When the top bit of the most-significant
> HOST_WIDE_INT in the absolute value is set, we implicitly sign-
>
On Oct 15, 2015, at 12:47 PM, Richard Sandiford
wrote:
> I can see that argument if people are only taking work items from
> the PR database. But it's possible (likely even) that people will
> independently find a problem like this and just fix it, if the missed
>
On Oct 15, 2015, at 1:38 PM, Richard Sandiford <richard.sandif...@arm.com>
wrote:
> Mike Stump <mikest...@comcast.net> writes:
>> On Oct 15, 2015, at 12:47 PM, Richard Sandiford
>> <richard.sandif...@arm.com> wrote:
>>> I can see that argument if people
On Oct 15, 2015, at 6:18 AM, Richard Sandiford
wrote:
> Stripping unnecessary sign ops at the gimple level means that we're
> no longer able to optimise:
>
> if (cos(y<10 ? -fabs(x) : tan(x<20 ? -x : -fabs(y)))
> != cos(y<10 ? x : tan(x<20 ? x : y)))
>
On Oct 12, 2015, at 3:32 PM, Chen Gang wrote:
>
> OK, thanks. If we really need to fix it, which target hook should I use?
> (or do we need a new target hook?)
So, the first discussion would be if it is, or is not a bug. If it isn’t, then
there is no fix. No fix,
So, I keep on seeing inaccurate schedule time on the conditional branches after
a store, and tracked it down to this type of solution. On my machine, I can
run these two in the same cycle, but with a REG_DEP_OUTPUT dependency it was
moving the branch to the next cycle. Now, I’ll plead
On Oct 7, 2015, at 6:08 AM, James Norris wrote:
> I've revised the patch based on the review comments from yourself,
> Bernd, and Joseph (thank you for your comments).
> OK?
Ok.
On Oct 5, 2015, at 7:47 AM, Richard Sandiford wrote:
> - return real_equal (_REAL_CST (expr), )
> + return real_equal (_REAL_CST (expr), <0> ())
On behalf of mere mortals, hiding the syntax <0> () into a header file
as in implementation detail is entirely
On Sep 28, 2015, at 5:35 AM, James Norris wrote:
> The attached patch fixes a problem when doing remote testing.
> Specifically, testing of the atomic tests found in gcc/atomic.
> The code in atomic_init precludes the setting of the variable
> 'link_flags' when doing
On Oct 5, 2015, at 9:46 AM, Steve Ellcey wrote:
> One example of an issue I have run into is with the DWARF unwind
> generation and 'Rule 16' in dwarf2cfi.c. It assumes the AND instruction
> has an integer constant argument but MIPS can't do an AND with a
> constant like -16
On Oct 4, 2015, at 11:15 AM, H.J. Lu wrote:
> Current stack alignment implementation requires at least
> one, maybe two, scratch registers:
So, I have some cases where I need scratch registers as well. I always save 2
registers and they go first (and restore last), so I
On Sep 30, 2015, at 1:04 AM, Richard Biener wrote:
> So what about a branch_cost hook that takes taken/not-taken probabilities as
> argument?
So, for my port, I need to know %prediction as well to calculate cost. I know,
kinda sucks. Or put another way, I want to
On Sep 29, 2015, at 1:59 PM, H.J. Lu wrote:
> commit f3a6675a8d69d810d2cad0c090a762094a0a8622
> Author: H.J. Lu
> Date: Tue Sep 29 13:47:18 2015 -0700
>
>Define EPILOGUE_USES in i386 so that all preserved registers are used
>by the epilogue of
On Sep 29, 2015, at 1:29 PM, Christophe Lyon wrote:
> The attached patch fixes the order on the few testcases where I
> noticed it was wrong.
> OK?
Ok.
On Sep 29, 2015, at 3:10 PM, H.J. Lu <hjl.to...@gmail.com> wrote:
> On Tue, Sep 29, 2015 at 2:23 PM, Mike Stump <mikest...@comcast.net> wrote:
>> On Sep 29, 2015, at 1:59 PM, H.J. Lu <hjl.to...@gmail.com> wrote:
>>> commit f3a6675a8d69d810d2cad0c090a76209
On Sep 29, 2015, at 2:23 PM, Mike Stump <mikest...@comcast.net> wrote:
> On Sep 29, 2015, at 1:59 PM, H.J. Lu <hjl.to...@gmail.com> wrote:
>> commit f3a6675a8d69d810d2cad0c090a762094a0a8622
>> Author: H.J. Lu <hjl.to...@gmail.com>
>> Date: Tue Sep
On Sep 29, 2015, at 3:40 PM, H.J. Lu wrote:
> How about adding a "no_caller_saved_registers" attribute?
You can save all call clobbered registers with 3 instructions? Really? I’m
skeptical. Anyway, if you do this by turning off great swaths of registers,
then, I guess
On Sep 29, 2015, at 1:16 PM, H.J. Lu <hjl.to...@gmail.com> wrote:
> On Tue, Sep 29, 2015 at 11:49 AM, Mike Stump <mikest...@comcast.net> wrote:
>> To be feature complete, it would be nice to have two styles of interrupt
>> functions, one that returns with iret, an
On Sep 29, 2015, at 7:31 AM, James Greenhalgh wrote:
> On Tue, Sep 29, 2015 at 11:16:37AM +0100, Richard Biener wrote:
>> On Fri, Sep 25, 2015 at 5:04 PM, James Greenhalgh
>> wrote:
>>>
>>> In relation to the patch I put up for review a few
To be feature complete, it would be nice to have two styles of interrupt
functions, one that returns with iret, and one that returns with ret. The
point is that the user might want to call functions from a interrupt handler
and not save and restore all call clobbered registers. By allowing a
On Sep 27, 2015, at 6:29 PM, Jeff Law wrote:
> I don't think we're there yet either -- many ports still require some
> guidance from Vlad to get working with LRA.
>
> It *may* be time to decree that any new ports must use the LRA path rather
> than reload. I'm still on the
On Sep 28, 2015, at 1:15 AM, Senthil Kumar Selvaraj
wrote:
> The below patch skips gcc.dg/addr_equal-1.c if the target keeps null
> pointer checks.
>
> The test fails for such targets (avr, in my case) because the address
> comparison in the below code does
On Sep 28, 2015, at 2:43 PM, Segher Boessenkool
wrote:
> Double-quoted words in Tcl have substitutions performed on them, including
> backslash substitutions. That isn't terribly nice for regular expressions,
> so use braced words instead.
>
> Tested on
On Sep 24, 2015, at 11:40 AM, David Edelsohn wrote:
> AIX added support for the initially missing DWARF sections.
> Bad news: The support is in an AIX service pack whose presence on a
> system requires effort to determine.
So, we faced this problem at Apple, and we just
On Sep 16, 2015, at 12:29 AM, Andreas Schwab <sch...@suse.de> wrote:
> Mike Stump <mikest...@comcast.net> writes:
>
>> The software presently works with 1.4.4 and there aren’t any changes
>> that require anything newer.
>
> SLES 12 has 1.4.4.
On Sep 16, 2015, at 12:29 AM, Andreas Schwab <sch...@suse.de> wrote:
> Mike Stump <mikest...@comcast.net> writes:
>
>> The software presently works with 1.4.4 and there aren’t any changes
>> that require anything newer.
>
> SLES 12 has 1.4.4.
On Sep 16, 2015, at 9:25 AM, Ramana Radhakrishnan
wrote:
>
> Sorry about the obvious (possibly dumb) question.
> Can't we just import a copy of dejagnu each year and install it as part of
> the source tree?
TL;DR: No.
We could, and indeed, some people do
On Sep 16, 2015, at 9:25 AM, Ramana Radhakrishnan
wrote:
>
> Sorry about the obvious (possibly dumb) question.
> Can't we just import a copy of dejagnu each year and install it as part of
> the source tree?
TL;DR: No.
We could, and indeed, some people do
On Sep 16, 2015, at 12:02 PM, Bernhard Reutner-Fischer
wrote:
> Where Joseph said he'd wait some more.. I had thought I asked longer ago than
> that, time flies if one has fun.
>
> I'd just require 1.5.3 just to avoid the time needed by folks to workaround
> those silly
On Sep 16, 2015, at 12:02 PM, Bernhard Reutner-Fischer
wrote:
> Where Joseph said he'd wait some more.. I had thought I asked longer ago than
> that, time flies if one has fun.
>
> I'd just require 1.5.3 just to avoid the time needed by folks to workaround
> those silly
On Sep 15, 2015, at 1:04 PM, Jeff Law wrote:
> Given we haven't updated the dejagnu reqs since ~2001, I think stepping
> forward would be appropriate and I'd support moving all the way to 1.5.3 with
> the expectation that we'll be on a cadence of no faster than 2 years going
>
On Sep 15, 2015, at 1:04 PM, Jeff Law wrote:
> Given we haven't updated the dejagnu reqs since ~2001, I think stepping
> forward would be appropriate and I'd support moving all the way to 1.5.3 with
> the expectation that we'll be on a cadence of no faster than 2 years going
>
On Sep 14, 2015, at 3:37 PM, Jeff Law wrote:
>> Maybe GCC-6 can bump the required
>> dejagnu version to allow for getting rid of all these superfluous
>> load_gcc_lib? *blink* :)
> I'd support that as a direction.
>
> Certainly dropping the 2001 version from our website in favor
On Sep 14, 2015, at 3:37 PM, Jeff Law wrote:
>> Maybe GCC-6 can bump the required
>> dejagnu version to allow for getting rid of all these superfluous
>> load_gcc_lib? *blink* :)
> I'd support that as a direction.
>
> Certainly dropping the 2001 version from our website in favor
On Sep 12, 2015, at 8:02 AM, Iain Sandoe wrote:
> OK for trunk?
So, does this work on 10.3? ppc? ppc64? You modify darwin.h, and that file
is used everywhere.
If it really works everywhere, Ok.
If it doesn’t, then it should be in a file that is used only on the
On Sep 12, 2015, at 7:33 AM, Iain Sandoe wrote:
> e) If a user elects to call a compiler (cc1*, f951, etc.) without a
> version-min, the init provided in (d) will kick in, and stop the compiler
> from segv-ing. However, we should warn the User that a default was used,
>
On Sep 13, 2015, at 1:59 PM, Iain Sandoe wrote:
> chose this comment carefully : " for something that's essentially a constant
> for the versions of ld that work with current GCC. “
> WDYT? I can revise the patch if you think there's a Better Way to do it.
So, I tried
On Sep 8, 2015, at 9:12 PM, Ian Lance Taylor wrote:
> Yes, I think this might be even better in code. How about something
> like
>
> /* On some versions of AIX O_CLOEXEC does not fit in int, so use a
> cast to force it. */
> descriptor = open (filename, (int) (O_RDONLY |
On Sep 3, 2015, at 9:45 AM, Jonathan Roelofs wrote:
> Moral of the story is: these tests fail in our environment, but only because
> the regexes do not expect the presence of the ansi color codes, and we can't
> trick the runtime into not emitting them.
When the user
On Sep 8, 2015, at 9:41 PM, David Miller wrote:
> +#define TARGET_LRA_P hook_bool_void_true
Are we at the point there this should be the default, and old ports should just
define to false, if they really need to? I’m using nothing but LRA as well.
On Sep 8, 2015, at 6:53 AM, David Edelsohn wrote:
> On Tue, Sep 8, 2015 at 9:51 AM, FX wrote:
>>> #define _FCLOEXEC 0x0010L
>>> #define O_CLOEXEC _FCLOEXEC /* sets FD_CLOEXEC on open */
>>
>> That’s weird, and definitely
On Sep 7, 2015, at 11:24 AM, Iain Sandoe wrote:
> For some Darwin compilers, "-arch " can be used (a) in place of, but to
> indicate the same as, a multilib flag like "-m32" and (b) multiple times to
> indicate that the User wants a FAT object with multiple arch
On Sep 7, 2015, at 8:23 AM, Iain Sandoe wrote:
> On Darwin platforms, when referenced from the main executable, it's permitted
> to access *_environ directly.
> OK for trunk and active branches?
Darwin bits Ok.
On Sep 4, 2015, at 4:10 AM, Hahnfeld, Jonas wrote:
* intelmic-mkoffload.c (prepare_target_image): Fix if the temp path
contains a '-‘.
So, out of curiosity, did you test all characters other than null? If -
doesn’t work, there is a good chance that
On Sep 4, 2015, at 8:02 AM, H.J. Lu wrote:
>> It's OK for me, but I can't approve it.
>
> I will check it in as an obvious fix.
Thanks, my 12/24 core box will appreciate it.
On Sep 4, 2015, at 2:45 PM, Ilya Verbin <iver...@gmail.com> wrote:
> 2015-09-04 22:27 GMT+03:00 Mike Stump <mikest...@comcast.net>:
>> On Sep 4, 2015, at 4:10 AM, Hahnfeld, Jonas <hahnf...@itc.rwth-aachen.de>
>> wrote:
>>>>>> * intelmic-mkoff
On Sep 1, 2015, at 3:05 AM, Sebastian Huber
wrote:
> libstdc++-v3/ChangeLog
> 2015-09-01 Sebastian Huber
>
>testsuite/*: Use 's/dg-do run.*\*-\*-cygwin\* /&*-*-rtems* /' to
>add RTEMS target selector to all tests
On Aug 30, 2015, at 8:36 PM, Michael Collison
wrote:
> Ping. Originally posted here:
>
> https://gcc.gnu.org/ml/gcc-patches/2015-08/msg01475.html
I looked at the patch and wondered if I had worked around the lack of the
feature in my port. I didn’t find any
These seem to be missing?
I stenciled this up by copy and pasting…
I did try and run the test suite, but you didn’t add a -L$(objdir) to the flags
to pick up the library that was built. You incorrectly test the installed
library, which has no relation to the library that should be tested.
On Aug 27, 2015, at 6:13 AM, Kaushik Phatak kaushik.pha...@kpit.com wrote:Hi
DJ,
I have worked out an updated patch, which would save the MDUC specific
registers
in the interrupt routine when the option '-msave-mduc-in-interrupts' is
passed.
This gets active only for the G13 targets.
So,
On Aug 25, 2015, at 1:14 AM, Christophe Lyon christophe.l...@linaro.org wrote:
Some subsets of the tests override ALWAYS_CXXFLAGS or
TEST_ALWAYS_FLAGS and perform effective_target support tests using
these modified flags.
This patch adds a new function 'clear_effective_target_cache', which
On Aug 20, 2015, at 12:29 AM, Richard Biener rguent...@suse.de wrote:
where the references always use positive offset and are based on the
next previous lable (so Ldebug_info_from_t1.c is not refering to
an entity at Ldebug_info_from_t2.c or beyond). So that seems to
follow the restrictions
On Aug 19, 2015, at 7:25 AM, Richard Biener rguent...@suse.de wrote:
This is needed so that we can output references to $early-debug-symbol +
constant offset where $early-debug-symbol is the beginning of a
.debug_info section containing early debug info from the compile-stage.
Constant
On Jun 15, 2015, at 7:30 AM, Kyrill Tkachov kyrylo.tkac...@arm.com wrote:
On 29/05/15 11:15, Kyrill Tkachov wrote:
On 29/05/15 10:08, Kyrill Tkachov wrote:
Hi Mike,
On 28/05/15 22:15, Mike Stump wrote:
So, the arm memcpy code of aligned data isn’t as good as it can be.
void *memcpy
On Aug 15, 2015, at 9:19 AM, Richard Sandiford rdsandif...@googlemail.com
wrote:
Mike Stump mikest...@comcast.net writes:
On Aug 15, 2015, at 3:32 AM, Richard Sandiford
rdsandif...@googlemail.com wrote:
The port is only buggy if they have define_peephole2s with match_scratches
and those
On Aug 15, 2015, at 3:32 AM, Richard Sandiford rdsandif...@googlemail.com
wrote:
The port is only buggy if they have define_peephole2s with match_scratches
and those match_scratches require a register that would be saved by
an interrupt function. In other cases defining T_H_R_S_O would have
On Aug 14, 2015, at 3:24 PM, Paolo Bonzini bonz...@gnu.org wrote:
There are plenty of targets that do not require -fPIC because they always
generate position independent code, but none of them feels the need to
complain with the user about an unnecessary but perfectly valid option,
on each and
On Aug 13, 2015, at 3:05 AM, Richard Biener richard.guent...@gmail.com wrote:
Ok, then guard the with __GCC__ and do the expensive bit stuff
otherwise. Just to cater for other host compilers doing sth unsensibly
implementation defined.
Ick. The guard should be specific to the
On Aug 13, 2015, at 12:54 PM, Richard Sandiford rdsandif...@googlemail.com
wrote:
It was discovered that with the attached test case compiled with -O2
-funroll-loops, the regrename pass renamed one of the registers ($2)
to $8 that was not saved by the prologue.
The attached patch fixes it
On Aug 12, 2015, at 7:43 PM, Segher Boessenkool seg...@kernel.crashing.org
wrote:
Yes. And there are much worse problems, like many things not working
right if your HOST_WIDE_INT would happen to be more than 64 bits; we
cannot really shake those out because there is no actual system to
test
On Aug 12, 2015, at 1:07 PM, Richard Sandiford rdsandif...@googlemail.com
wrote:
I don't think the right shifts are an issue at all.
Well, they're implementation-defined, at least in C.
The C11 wording for E1 E2 is If E1 has a signed type and a negative
value, the
resulting value is
On Aug 12, 2015, at 11:07 AM, Jeff Law l...@redhat.com wrote:
On 08/12/2015 11:12 AM, Richard Biener wrote:
Prec is almost never a constant and is heavily used from wide-int.
We are not exploiting this undefined ness in C so I object to making this so
much slower.
Can we instead do
On Aug 11, 2015, at 12:08 PM, Caroline Tice cmt...@google.com wrote:
When bootstrapping on darwin with vtable verificaiton enabled,
libstdc++ is giving a lot of warnings due to a flag in
VTV_CXXLINKFLAGS that has a slightly different format for darwin than
for linux. This patch (actually
On Aug 4, 2015, at 5:30 AM, H.J. Lu hjl.to...@gmail.com wrote:
Where does this feature belong?
I prefer the middle end.
On Aug 4, 2015, at 8:44 AM, H.J. Lu hjl.to...@gmail.com wrote:
On Tue, Aug 4, 2015 at 8:40 AM, Mike Stump mikest...@comcast.net wrote:
On Aug 4, 2015, at 5:30 AM, H.J. Lu hjl.to...@gmail.com wrote:
Where does this feature belong?
I prefer the middle end.
Any comments on my middle-end
On Jul 28, 2015, at 6:38 AM, Bruce Korb bk...@gnu.org wrote:
Definitely much better. I won't apply it until the weekend, so
someone else will likely beat me to it.
Looks good to me as well, I checked it in.
Committed revision 226317.
On Jul 27, 2015, at 7:36 PM, Eric Gallager eg...@gwmail.gwu.edu wrote:
On 7/27/15, Andreas Schwab sch...@linux-m68k.org wrote:
Eric Gallager eg...@gwmail.gwu.edu writes:
Okay, I tried embedding ! -name CVS/ ! -name .svn/ into the find
-name does an exact match, so you don't need the slash.
On Jul 23, 2015, at 7:47 AM, H.J. Lu hjl.to...@gmail.com wrote:
On Fri, Jul 17, 2015 at 7:43 AM, H.J. Lu hjl.to...@gmail.com wrote:
On Wed, Jul 15, 2015 at 9:47 AM, Mike Stump m...@mrs.kithrup.com wrote:
On Jul 15, 2015, at 9:07 AM, H.J. Lu hjl.to...@gmail.com wrote:
On Wed, Jul 15, 2015 at 1
On Jul 21, 2015, at 1:32 PM, Sebastian Pop seb...@gmail.com wrote:
Thanks Jeff.
Could somebody with access to sourceware.org upload a tar.bz2 of the required
version of isl from http://isl.gforge.inria.fr/isl-0.15.tar.bz2?
Also, once that is done, I will commit the following patch
On Jul 17, 2015, at 2:28 AM, Mikhail Maltsev malts...@gmail.com wrote:
The following code (reduced from wide-int.h) is rejected by Intel C++ Compiler
(EDG-based):
So, could you test this with the top of the tree compiler and file a bug report
against g++ for it, if it seems to not work right.
On Jul 15, 2015, at 9:07 AM, H.J. Lu hjl.to...@gmail.com wrote:
On Wed, Jul 15, 2015 at 1:03 AM, Jan Beulich jbeul...@suse.com wrote:
- $gcc_cv_as_gas_srcdir/configure.in \
+ $gcc_cv_as_gas_srcdir/configure.[ai][cn] \
$gcc_cv_as_gas_srcdir/Makefile.in ; do
On Jul 11, 2015, at 4:58 AM, Dan Nagle danlna...@mac.com wrote:
The standard is written in standardese, not English.
While what you say is true, sorry, shall _is_ English:
used in laws, regulations, or directives to express what is mandatory
I’d like to merge in the fix from https://gcc.gnu.org/PR66523 into the
gcc-5-branch.
RM Ok?
https://gcc.gnu.org/bugzilla/attachment.cgi?id=35773:
diff --git a/gcc/config/darwin.c b/gcc/config/darwin.c
index 40804b8..0080299 100644
--- a/gcc/config/darwin.c
+++ b/gcc/config/darwin.c
@@ -1259,6
On Jul 3, 2015, at 4:16 AM, Carlos Sánchez de La Lama csanchez...@gmail.com
wrote:
PR52482 seems to be cause by old gas not supporting named parameters in
macros. Xcode-2.5 (last available for OSX PPC) gas version is 1.38.
Patch is against gcc-4.8.4, but affected lines have not changed in
On Jun 30, 2015, at 10:38 AM, Martin Sebor mse...@gmail.com wrote:
In the debian reproducible builds project we have considered several
options to address this issue. We considered redefining the __DATE__ and
__TIME__ defines by command line flags passed to gcc, but as you say,
that triggers
On Jun 26, 2015, at 9:09 AM, Jack Howarth howarth.at@gmail.com wrote:
The attached revised patch adjusts the tests for the filds and fists
mnemonics to use the assembly...
filds (%ebp); fists (%ebp)
and the test for the fildq and fistq mnemonics to use the assembly...
fildq (%ebp);
On Jun 10, 2015, at 10:16 AM, David Malcolm dmalc...@redhat.com wrote:
It doesn't have an output formatter for the DejaGnu format, but I guess
I could write one. The gtest standard output format is IMHO superior to
DejaGnu's since it tells you start-of-test/end-of-test on separate
lines, so
On Jun 19, 2015, at 5:36 PM, David Edelsohn dje@gmail.com wrote:
Maybe you should ask Richi or Jakub about the testcase because you are
placing it in a non-target-specific location. It should succeed on
all targets, but it may expose latent bugs on other targets.
A latent bug is one that
On Jun 18, 2015, at 3:10 AM, Richard Biener rguent...@suse.de wrote:
Ok for trunk?
Ok.
601 - 700 of 3045 matches
Mail list logo