On Mon, 30 Jun 2014, David Wohlferd wrote:
I don't have permissions to commit this patch, but I do have a release on file
with the FSF.
Problem description:
The text for using Explicit Register Variables is confusing, redundant, and
fails to make certain essential information clear.
[...]
Oops. I've left cris-linux and crisv32-linux alone and rot set
in...quite some time ago. The prerequisite config.gcc I kind of
knew about, but it fell in and out of mind; it was finally noted
in the referenced PR, but just as a side-comment. Regarding the
removed comment, there seems to be
On Fri, 18 Jul 2014, Jan-Benedict Glaw wrote:
Hi!
As a leftover of r210931, an unused variable resulted in:
g++ -c -g -O2 -DIN_GCC -DCROSS_DIRECTORY_STRUCTURE -fno-exceptions
-fno-rtti -fasynchronous-unwind-tables -W -Wall -Wno-narrowing
-Wwrite-strings -Wcast-qual
On Fri, 18 Jul 2014, Jan-Benedict Glaw wrote:
This was a build using GCC's ./contrib/config-list.mk to do the build.
It passes --enable-werror-always to top-level `configure', this is
where the -Werror comes from.
Aha. Looks like it's of more use than theoretical pain; sounds
like this should
On Tue, 22 Jul 2014, Richard Biener wrote:
On Fri, 18 Jul 2014, Hans-Peter Nilsson wrote:
On Fri, 18 Jul 2014, Jan-Benedict Glaw wrote:
It should be per-target because there *may* be port-specific
constructs warned about by buggy previous-but-not-ancient
gcc-versions, where working
On Tue, 22 Jul 2014, Mike Stump wrote:
On Jul 22, 2014, at 1:40 PM, Hans-Peter Nilsson h...@bitrange.com wrote:
*Developers* (or rather, people cross-building non-released gcc
source in their usual setup) don't use the fairly old or even
broken host gcc versions that can be expected
On Thu, 24 Jul 2014, Jan-Benedict Glaw wrote:
On Tue, 2014-07-22 16:40:31 -0400, Hans-Peter Nilsson h...@bitrange.com
wrote:
Jan-Benedict, which host gcc version do you use when getting
most targets to build with config-list.mk? Maybe we can just
set the initial version to that instead
On Fri, 25 Jul 2014, Jan-Benedict Glaw wrote:
On Thu, 2014-07-24 16:30:13 -0400, Hans-Peter Nilsson h...@bitrange.com
wrote:
On Thu, 24 Jul 2014, Jan-Benedict Glaw wrote:
On Tue, 2014-07-22 16:40:31 -0400, Hans-Peter Nilsson h...@bitrange.com
wrote:
Jan-Benedict, which host gcc
On Fri, 25 Jul 2014, Hans-Peter Nilsson wrote:
Anyway, on to the point of this message: by the quoted list it
seems you have a local host called pluto using 4.9.1 as the host
gcc for some build; does config-list.mk work for that?
Never mind, I found a 4.9.1 installation on gcc110
On Sat, 20 Sep 2014, Jan-Benedict Glaw wrote:
Please note that nios2 failed in the same way a number of other
targets fail, too:
cr16-elf
http://toolchain.lug-owl.de/buildbot/show_build_details.php?id=351532
fr30-elf
On Fri, 4 Apr 2014, dw wrote:
Problem description:
The existing documentation does an inadequate job of describing gcc's
implementation of the asm keyword. This has led to a great deal of
confusion as people struggle to understand how it works. This entire section
requires a rewrite that
On Mon, 31 Mar 2014, Dominique d'Humières wrote:
Updated gfortran.dg/fmt_en.f90 to skip some tests not
supported on i?86-*-solaris2.9* and hppa*-*-hpux* (these tests
assume rounding to nearest and to even on tie, AFAICT
i?86-*-solaris2.9* rounds real(16) to zero and hppa*-*-hpux*
rounds all
On Sat, 12 Apr 2014, Dominique Dhumieres wrote:
This test, after the update on 4.8 in r209070 when the test-case was
modified substantially (not really covered by the ChangeLog entry) to be
identical to that on trunk, apparently takes a different route in the
fortran run-time library on
On Tue, 8 Apr 2014, dw wrote:
The general bits seems like a big improvement, but what worries
me is the deleted text. For example, the aspects of Explicit
Reg Vars when *directly feeding an asm* and how to write them
to avoid the named registers being call-clobbered between
assignment
On Sun, 13 Apr 2014, dw wrote:
So, how about this:
1) I put the (rephrased) text and examples at the end of Local Reg Vars page
(starts with Sometimes):
http://www.LimeGreenSocks.com/gcc/Local-Reg-Vars.html
2) In the constraint paragraph for both Input and Output, I added this: If
you must
On Fri, 11 Apr 2014, Jakub Jelinek wrote:
On Thu, Apr 10, 2014 at 02:18:26PM +0100, Ramana Radhakrishnan wrote:
I see failures from last night on aarch64-none-elf and arm-none-eabi
(both bare-metal) configurations even after moving up to dejagnu
1.5.1. If this can't be fixed easily should
On Mon, 14 Apr 2014, Jakub Jelinek wrote:
On Sun, Apr 13, 2014 at 09:24:28PM -0400, Hans-Peter Nilsson wrote:
On Fri, 11 Apr 2014, Jakub Jelinek wrote:
On Thu, Apr 10, 2014 at 02:18:26PM +0100, Ramana Radhakrishnan wrote:
I see failures from last night on aarch64-none-elf and arm-none
Its BRANCH_COST being the default, MMIX is one of them, here
doing away with a few regressions. Committed.
gcc/testsuite:
* lib/target-supports.exp
(check_effective_target_logical_op_short_circuit): Add mmix-*-*
to the list.
Index: gcc/testsuite/lib/target-supports.exp
That test now looks a bit silly with the dozen+1 exceptions. But, I
guess with just this one(?) test there's little sense in adding an
effective target to describe that division by 0 doesn't signal. Other
than keeping it in just one place, of course. But, committed.
gcc/testsuite:
*
On Thu, 24 Apr 2014, Jeff Law wrote:
On 04/16/14 18:20, seg...@kernel.crashing.org wrote:
PR target/60822
2014-04-16 Segher Boessenkool seg...@kernel.crashing.org
* config/m68k/m68k.md (extendplussidi): Don't allow memory for
operand 1.
Thanks. I tweaked the comment and
On Tue, 13 May 2014, Joseph S. Myers wrote:
On Mon, 12 May 2014, Hans-Peter Nilsson wrote:
On Thu, 24 Apr 2014, Jeff Law wrote:
On 04/16/14 18:20, seg...@kernel.crashing.org wrote:
PR target/60822
2014-04-16 Segher Boessenkool seg...@kernel.crashing.org
* config
On Mon, 5 May 2014, Jan Hubicka wrote:
Hi,
this patch fixes unfortunate thinko in get_class_context that invalidates
transitions from non-POD type to a polymorphic type that may happen by virtue
of placement new and apparently breaks openJDK and Qt. I really tried to keep
placement new in
On Mon, 19 May 2014, Janne Blomqvist wrote:
Hello,
some systems such as GNU Hurd, don't define PATH_MAX at all, and on
some other systems many syscalls apparently work for paths longer than
PATH_MAX. Thus GFortran shouldn't truncate paths to PATH_MAX
characters, but rather use heap allocated
On Fri, 23 May 2014, Janne Blomqvist wrote:
On Thu, May 22, 2014 at 6:36 PM, Hans-Peter Nilsson h...@bitrange.com wrote:
This patch broke build for newlib targets; you need AC_DEFINE
clauses for those in the if-then-leg where you patched the
else-leg.
Do I?
The way that configure-clause
Apparently LTO improved or at least changed between r21 and
r211121, such that memory outside the defined space was wrongly read
as expected for this test-case, corresponding to the wrongly
presumed stacked parameters. For a normal target this would
correspond to a SEGV. You'd need the
On Mon, 5 May 2014, Dominique Dhumieres wrote:
With the following patch, gfortran can be regtested with -flto
with no failure, but pr54852 and pr60061.
OK for trunk?
Dominique
2014-05-05 Dominique d'Humieres domi...@lps.ens.fr
* gfortran.dg/gfortran.dg/bind_c_array_params_2.f90:
On Tue, 10 Jun 2014, Maciej W. Rozycki wrote:
Hi,
I've noticed mmix_asm_output_source_line is declared, but nowhere
defined. OK to remove the prototype?
Sure; in fact, obvious.
brgds, H-P
On Wed, 11 Jun 2014, Jan Hubicka wrote:
* varasm.c (set_implicit_section): New function.
(resolve_unique_section): Use it to set implicit section
for aliases, too.
(get_named_text_section): Use symtab_get_node (decl)-implicit_section
(default_function_section):
On Sat, 14 Jun 2014, Richard Sandiford wrote:
To make the final representation change easier, this patch introduces
macros for iterating over lists of defs, uses and eq_uses. At the
moment there are three possible keys when accessing df_ref lists:
the insn rtx (DF_INSN_*), the insn uid
On Sun, 15 Jun 2014, Steven Bosscher wrote:
On Sun, Jun 15, 2014 at 1:27 PM, Hans-Peter Nilsson wrote:
/tmp/hpautotest-gcc0/gcc/gcc/auto-inc-dec.c: In function 'void
merge_in_block(int, basic_block_def*)':
/tmp/hpautotest-gcc0/gcc/gcc/auto-inc-dec.c:1442: error: 'uid'
was not declared
On Sun, 15 Jun 2014, Hans-Peter Nilsson wrote:
On Sun, 15 Jun 2014, Steven Bosscher wrote:
Can you please try:
[...]
Thanks. Looks pretty obvious. I was heading for the door with
just enough time to report the issue, so I didn't actually look
at the code before. I'll commit
On Sun, 15 Jun 2014, Hans-Peter Nilsson wrote:
On Sun, 15 Jun 2014, Hans-Peter Nilsson wrote:
On Sun, 15 Jun 2014, Steven Bosscher wrote:
Can you please try:
[...]
Thanks. Looks pretty obvious. I was heading for the door with
just enough time to report the issue, so I didn't
On Mon, 16 Jun 2014, Steven Bosscher wrote:
On Mon, Jun 16, 2014 at 12:36 AM, Hans-Peter Nilsson wrote:
On Sun, 15 Jun 2014, Steven Bosscher wrote:
On Sun, Jun 15, 2014 at 1:27 PM, Hans-Peter Nilsson wrote:
/tmp/hpautotest-gcc0/gcc/gcc/auto-inc-dec.c: In function 'void
merge_in_block
On Mon, 27 Jan 2014, Bruce Korb wrote:
On Sun, Jan 26, 2014 at 9:38 PM, Hans-Peter Nilsson h...@bitrange.com wrote:
On Sun, 8 Dec 2013, Bruce Korb wrote:
On 12/08/13 13:06, Gerald Pfeifer wrote:
Lovely. Thank you very much!
(Looks like nobody replied to this and it isn't committed
On Mon, 27 Jan 2014, Richard Biener wrote:
Huh, so we have C for cross-builds and C++ for bootstraps.
No, we use a C host compiler in both cases. Only stages 2 and 3 build with a
C++ compiler.
Tomatos potatoes! As fortran isn't built until then, it'll be
built as C for cross-builds and C++
On Tue, 28 Jan 2014, Andreas Schwab wrote:
Hans-Peter Nilsson h...@bitrange.com writes:
See is_release in that same configure.ac, that might be the only
additional condition that's needed.
is_release only distinguishes a release from a snapshot, but does not
say anything whether its
On Tue, 4 Feb 2014, Rainer Orth wrote:
AFAICT the gcc.dg/binop-xor1.c test is XPASSing everywhere since about
20131114:
Bah, missing analysis. Everywhere does not include cris-elf,
powerpc64-unknown-linux-gnu, m68k-unknown-linux-gnu,
s390x-ibm-linux-gnu, powerpc-ibm-aix7.1.0.0.
XPASS:
On Thu, 13 Feb 2014, Richard Sandiford wrote:
Richard Sandiford rsand...@linux.vnet.ibm.com writes:
Hans-Peter Nilsson h...@bitrange.com writes:
On Tue, 4 Feb 2014, Rainer Orth wrote:
AFAICT the gcc.dg/binop-xor1.c test is XPASSing everywhere since about
20131114:
Bah, missing
On Fri, 14 Feb 2014, Jakub Jelinek wrote:
On Fri, Feb 14, 2014 at 10:37:03AM -0700, Jeff Law wrote:
On 02/13/14 03:54, Richard Sandiford wrote:
Richard Sandiford rsand...@linux.vnet.ibm.com writes:
Hans-Peter Nilsson h...@bitrange.com writes:
On Tue, 4 Feb 2014, Rainer Orth wrote
There was a new effective-target predicate (thanks, Richard S),
but the droplet that broke the camel's back or something, wasn't
added to its target-list. Committed after brief testing
(checking that tests fail before, checking that tests pass after
patch).
Other observations:
-
On Tue, 25 Feb 2014, bin.cheng wrote:
Hi,
This patch is to fix regression reported in PR60280 by removing forward loop
headers/latches in cfg cleanup if possible. Several tests are broken by
this change since cfg cleanup is shared by all optimizers. Some tests has
already been fixed by
On Mon, 3 Mar 2014, Richard Sandiford wrote:
AIUI:
Reading back the references don't yield any dissenting
flash-backs, FWIW.
So, a (use fp) then a (clobber fp)? That was probably just too
weird for me to think of, much like a hypercorrect ending of the
previous clause. :)
Thanks for dealing
From: Richard Biener rguent...@suse.de
Date: Thu, 23 Oct 2014 10:47:43 +0200
This adds a libcpp host module without NLS and ICONV support
and properly links genmatch against the build libcpp instead of
the host one.
Bootstrap running on x86_64-unknown-linux-gnu (stage1 all-gcc
finished
From: Hans-Peter Nilsson h...@axis.com
Date: Fri, 24 Oct 2014 06:32:06 +0200
The libcpp configure checks are actually run with gcc which is
bogus by itself, but apparently working. I guess the C vs. C++
declaration etc. differences for libcpp are mostly hidden by
using _GNU_SOURCE (through
From: Richard Biener rguent...@suse.de
Date: Fri, 24 Oct 2014 09:56:51 +0200
On Fri, 24 Oct 2014, Hans-Peter Nilsson wrote:
Still, I don't understand exactly how your patch
introduces build-subdirectories where there were none before.
Maybe that +all-gcc: maybe-all-build-libcpp was wrong
Sorry for the context-less mail but I didn't find a proper
obvious gcc-patches-message to reply to. (Also, I can't log
into bugzilla because to enter a PR as there appears to have
been some SSL changes such that my old firefox and gcc.gnu.org
can no longer agree on a cipher or something.) But,
From: David Malcolm dmalc...@redhat.com
Date: Fri, 29 Aug 2014 13:40:49 +0200
Patch attached, which fixes the above testcase; bootstrap in progress:
gcc/
* resource.h (mark_target_live_regs): Undo erroneous conversion
of second param of r214693, converting it back from
From: David Malcolm dmalc...@redhat.com
Date: Fri, 29 Aug 2014 13:26:59 +0200
On Fri, 2014-08-29 at 06:13 +0200, Hans-Peter Nilsson wrote:
/tmp/hpautotest-gcc1/cris-elf/gccobj/./gcc/xgcc
-B/tmp/hpautotest-gcc1/cris-elf/gccobj/./gcc/ -nostdinc
-B/tmp/hpautotest-gcc1/cris-elf/gccobj/cris
From: David Malcolm dmalc...@redhat.com
Date: Fri, 29 Aug 2014 17:33:54 +0200
On Fri, 2014-08-29 at 16:48 +0200, Hans-Peter Nilsson wrote:
Sorry, but that didn't help. I still get the exact same error.
(Yep, I double-checked that I didn't goof testing...)
Famous last words...
Fully
From: David Malcolm dmalc...@redhat.com
Date: Fri, 29 Aug 2014 20:07:04 +0200
BTW, in another email in the thread you said:
Thanks for the heads-up. BTW, the ChangeLog entries should say
what not why; that goes into a comment in the source.
OK. Where possible I've added comments in
In a native x86_64-linux toolchain in which
eh-table-registration is done explicitly (i.e. dl_iterate_phdr
and PT_GNU_EH_FRAME is *not* assumed, as that eliminates the
issue), the memory overhead for exception-initialization goes
beyond the 32768 bytes assumed in badalloc1.C and the test fails
for
The conditions for inhibit_libc to activate (i.e. for library
headers to be absent) are IMO a bit too automatic and the effect
is too subtle and serious in some situations. For example, if
you pre-install target headers in $target_header_dir, gcc will
find them and use them, but still
The directory at $target_header_dir is already inspected in
gcc/configure, for e.g. glibc version and stack protector
support, but not for setting inhibit_libc. This is just
inconsistent and the obvious resolution to me is to inhibit
inhibit_libc when a target *does* have its own set of headers,
This adds an option to allow programs and libraries built
*without* inhibit_libc to stay compatible with system libraries
(really: libgcc_s.so.1) built *with* inhibit_libc, at the cost
of the registration. As mentioned, that's a one-way
compatibility barrier.
While it's nice to avoid the
From: Joseph S. Myers jos...@codesourcery.com
Date: Fri, 5 Sep 2014 19:21:04 +0200
This patch removes some fp-bit target macros that are no longer
needed:
* __make_dp was not really designed as a target macro, but CRIS
defined it in cris.h anyway for optimization purposes
Minor
(Thanks to people CC'ed and others forgotten; I hope I
incorporated at least some of everyone's suggestions.)
First, as noted, the instructions are outdated due to repos merging,
splitting, moving and switching, with fallout such as it now seemed
odd as-is with one minor component randomly being
On Wed, 10 Sep 2014, Oleg Endo wrote:
On Wed, 2014-09-10 at 15:46 -0400, Hans-Peter Nilsson wrote:
(Thanks to people CC'ed and others forgotten; I hope I
incorporated at least some of everyone's suggestions.)
[...]
Also, the idea of using a *combined* tree here, has been challenged
Ping! http://gcc.gnu.org/ml/gcc-patches/2014-09/msg00402.html
From: Hans-Peter Nilsson h...@axis.com
Date: Thu, 4 Sep 2014 23:40:40 +0200
The directory at $target_header_dir is already inspected in
gcc/configure, for e.g. glibc version and stack protector
support, but not for setting
Ping! http://gcc.gnu.org/ml/gcc-patches/2014-09/msg00403.html
From: Hans-Peter Nilsson h...@axis.com
Date: Thu, 4 Sep 2014 23:42:28 +0200
This adds an option to allow programs and libraries built
*without* inhibit_libc to stay compatible with system libraries
(really: libgcc_s.so.1) built
On Wed, 17 Sep 2014, Janne Blomqvist wrote:
On Tue, Sep 16, 2014 at 11:17 AM, FX fxcoud...@gmail.com wrote:
2014-09-05 Janne Blomqvist j...@gcc.gnu.org
PR libfortran/62768
* io/io.h (gfc_unit): Store C string for the filename.
* io/close.c (st_close): Use gfc_unit.filename.
On Wed, 17 Sep 2014, Janne Blomqvist wrote:
/tmp/hpautotest-gcc1/gcc/libgfortran/io/inquire.c:97:41: error: 'gfc_unit'
has no member named 'file'
fstrcpy (iqp-name, iqp-name_len, u-file, u-file_len);
^
On Wed, 17 Sep 2014, Hans-Peter Nilsson wrote:
On Wed, 17 Sep 2014, Janne Blomqvist wrote:
Oops, I forgot to update some parts in an #ifdef branch that isn't
taken on my target. I'll try to find time to fix it later tonight. If
you're in a hurry, just replace
fstrcpy (iqp-name, iqp
On Wed, 17 Sep 2014, Hans-Peter Nilsson wrote:
On Wed, 17 Sep 2014, Hans-Peter Nilsson wrote:
On Wed, 17 Sep 2014, Janne Blomqvist wrote:
Oops, I forgot to update some parts in an #ifdef branch that isn't
taken on my target. I'll try to find time to fix it later tonight. If
you're
On Thu, 18 Sep 2014, Janne Blomqvist wrote:
On Wed, Sep 17, 2014 at 11:36 PM, Hans-Peter Nilsson h...@bitrange.com
wrote:
On the other hand, the tree *is* broken for some ports; I'd
prefer regressions to that. So, unless you're onto this, how do
you feel about me committing the posted
On Thu, 18 Sep 2014, Janne Blomqvist wrote:
On Thu, Sep 18, 2014 at 12:57 AM, Hans-Peter Nilsson h...@bitrange.com
wrote:
'k so we'll track the regressions in a PR.
Do you prefer to tack on to 62768 or a new PR?
Hijacking 62768 for the purposes of reporting a regression for
its fix would
On Wed, 17 Sep 2014, Hans-Peter Nilsson wrote:
On Thu, 18 Sep 2014, Janne Blomqvist wrote:
On Thu, Sep 18, 2014 at 12:57 AM, Hans-Peter Nilsson h...@bitrange.com
wrote:
'k so we'll track the regressions in a PR.
Do you prefer to tack on to 62768 or a new PR?
Hijacking 62768
On Thu, 18 Sep 2014, Janne Blomqvist wrote:
If you look back at the patch I posted, there's a
typo. :-} Duly warned about, but I'd rather expect the build to
fail.
Yes, strange that it didn't fail. There's no prototype for cf_fstrcpy,
and since we use std=gnu11 prototypes should be
From: Jeff Law l...@redhat.com
Date: Fri, 19 Sep 2014 08:29:16 +0200
On 09/12/14 11:51, Hans-Peter Nilsson wrote:
Ping! http://gcc.gnu.org/ml/gcc-patches/2014-09/msg00403.html
libgcc:
* crtstuff.c [EH_FRAME_SECTION_NAME !USE_PT_GNU_EH_FRAME]:
Sanity-check
From: Thomas Schwinge tho...@codesourcery.com
Date: Tue, 23 Sep 2014 23:21:05 +0200
Hi!
On Thu, 4 Sep 2014 23:40:40 +0200, Hans-Peter Nilsson hans-peter.nilsson@a=
xis.com wrote:
The directory at $target_header_dir is [...]
gcc:
* configure.ac (target_header_dir): Move block
On Tue, 15 Jan 2013, Janis Johnson wrote:
Most of the tests in gcc.c-torture/execute/builtins that use LTO torture
options -O2 -flto -fuse-linker-plugin -fno-fat-lto-objects fail to
link on EABI and ELF targets with multiple definitions for either memset
or strlen. I filed PR testsuite/55994
Ever since it was changed to a run test (from the default
compile, i.e. just producing assembly code), the test
gfortran.dg/inquire_10.f90 has failed for newlib targets while
linking, because (besides cygwin and some linux support), newlib
doesn't have getcwd:
/tmp/ccNhxU2l.o: In function
From: Janne Blomqvist blomqvist.ja...@gmail.com
Date: Sun, 20 Jan 2013 20:14:11 +0100
On Sun, Jan 20, 2013 at 2:29 AM, Hans-Peter Nilsson
hans-peter.nils...@axis.com wrote:
Ever since it was changed to a run test (from the default
compile, i.e. just producing assembly code), the test
On Mon, 14 Mar 2011, Benjamin Kosnik wrote:
Ugh. While doing other things I realized that the namespace versioning
for regex header files is off: it's not on the inner-most nested
namespace.
Fixed thusly.
But it seems like it's not committed?
brgds, H-P
On Wed, 16 Mar 2011, Benjamin Kosnik wrote:
Needs some more work, here's a rough draft.
s/Porting to the new tools/Porting to the new version/
?
brgds, H-P
On Tue, 29 Mar 2011, Vladimir Makarov wrote:
2011-03-29 Vladimir Makarov vmaka...@redhat.com
PR target/48336
PR middle-end/4834
(A typo here, 48342. Or maybe also needed for 48334?)
PR rtl-optimization/48345
* ira-color.c (setup_conflict_profitable_regs):
On Tue, 29 Mar 2011, Joseph S. Myers wrote:
Other cleanups here:
cris*-*-none acts just like cris*-*-elf in
config.gcc so it's appropriate to make the * subcase of cris*-*-* act
like the -elf case;
'k.
mmix-*-* disabled libgloss, i.e. libgloss for the
host, which is never built anyway.
Date: Thu, 31 Mar 2011 13:39:05 +0200
From: Ira Rosen ira.ro...@linaro.org
This patch changes NEON's default vector size from 64 to 128 bits.
I'm wondering, are there NEON-specific measurements to support
this change?
A colleague of mine implemented support for 64- and 128-bit NEON
for RAPP
On Sat, 2 Apr 2011, Joseph S. Myers wrote:
* cris-protos.h had an unused STDIO_INCLUDED definition, which I
removed.
Been there since the first commit, it seems.
Certainly this bit is ok.
A nit: you had several lines consisting of TAB*. (with the
obvious expansion) in the changelogs you
On Sun, 3 Apr 2011, Xinliang David Li wrote:
2011-04-03 Xinliang David Li davi...@google.com
* final.c (dump_basic_block_info): New function.
+ fprintf (file, # BLOCK %d, bb-index);
Random spotting: please use ASM_COMMENT_START instead of the
naked #.
brgds, H-P
On Mon, 4 Apr 2011, Richard Sandiford wrote:
Pretty much as the subject says.
OK to install?
CRIS and MMIX parts are ok.
brgds, H-P
PS. FWIW anyone: for my targets, a CC to me usually gets a faster response.
On Fri, 16 Sep 2011, David Miller wrote:
I've been meaning to toss something like this together for a while.
If we were going to do this, I wanted to get it out of the way before
adding VIS2 and VIS3 support.
While revisiting VIS, *please* consider fixing a big usability
problem: the pack
On Wed, 21 Sep 2011, David Miller wrote:
From: Hans-Peter Nilsson h...@bitrange.com
Date: Wed, 21 Sep 2011 21:27:08 -0400 (EDT)
While revisiting VIS, *please* consider fixing a big usability
problem: the pack and aligndata builtins don't take GSR in
account; it has unknown state and might
On Thu, 22 Sep 2011, David Miller wrote:
Positive feedback for the fact that someone is at least working on
this stuff at all would be appreciated as well.
Using it or working on it? Not that much of either, sorry, but
what I found when using it, I put in PR48974 (well, besides the
ICE's,
On Sat, 24 Sep 2011, David Miller wrote:
Hans, here is what I'm playing with right now against current
trunk.
A spot-check review:
I looked at the use cases for making use of the scale factor in the
VIS %gsr register and it's used similar to how rounding modes are
modified in the FPU
On Sat, 24 Sep 2011, David Miller wrote:
From: Hans-Peter Nilsson h...@bitrange.com
Date: Sat, 24 Sep 2011 17:15:06 -0400 (EDT)
I'd prefer it as a parameter to the builtins (expanding to two
insns, letting gcc get rid of the redundant ones; let the
initialization value be 0). I understand
On Sat, 24 Sep 2011, David Miller wrote:
From: Hans-Peter Nilsson h...@bitrange.com
Date: Sat, 24 Sep 2011 18:37:33 -0400 (EDT)
BTW, don't forget to clobber GSR at call insns!
This I explicitly want to avoid and is an explicit design decision.
Aha, now I get it; that's certainly key
On Sun, 25 Sep 2011, David Miller wrote:
For some reason I can't take ownership of your PR and mark it
closed, otherwise I'd do so as well.
Done, thanks. The most common cause is not using your
gcc.gnu.org account in bugzilla, needed to get those
superpowers. (For future reference, marking
Date: Sun, 2 Oct 2011 21:36:50 +0400
From: Anatoly Sokolov ae...@post.ru
OK to install?
* config/cris/m32c.c (cris_output_addr_const_extra): Make static.
(TARGET_OUTPUT_ADDR_CONST_EXTRA): Define.
* config/cris/cris.h
On Mon, 3 Oct 2011, David Miller wrote:
* config/sparc/sparc.md (bmaskP:mode_vis): Split into explicit 'di'
and 'si' patterns which describe the GSR changes explicitly in the
RTL using zero_extract.
(bshuffleV64I:mode_vis): Put the GSR use inside of the unspec.
(Heh,
On Fri, 30 Sep 2011, Artem Shinkarov wrote:
gcc/doc
* extend.texi: Adjust.
Pretty please document the new pattern names in doc/md.texi as
well. Thanks in advance.
brgds, H-P
On Thu, 6 Oct 2011, Artem Shinkarov wrote:
Successfully regtested on x86-unknown-linux-gnu. Committed to the
mainline with the revision 179588.
ChangeLog:
2011-10-06 Artjoms Sinkarovs artyom.shinkar...@gmail.com
* c-tree.h (c_expr_t): New typedef for struct c_expr.
On Thu, 6 Oct 2011, Artem Shinkarov wrote:
On Thu, Oct 6, 2011 at 3:27 AM, Hans-Peter Nilsson h...@bitrange.com wrote:
Write that changelog entry as:
PR middle-end/50607
* c-tree.h (c_expr_t): New typedef for struct c_expr.
(C_EXPR_APPEND): New macro.
* c
Date: Sun, 9 Oct 2011 17:47:22 +0400
From: Anatoly Sokolov ae...@post.ru
OK to install?
* config/cris/cris.c (cris_preferred_reload_class): New function.
(TARGET_PREFERRED_RELOAD_CLASS): Define.
* config/cris/cris.h (OUTPUT_ADDR_CONST_EXTRA): Remove.
On Mon, 19 Sep 2011, Ulrich Weigand wrote:
Richard Earnshaw wrote:
On 19/09/11 15:14, Ulrich Weigand wrote:
So it seems to me that for match_operator operands, the
goal_alternative_win flag should always be true ...
Can you find out why this isn't true in your case?
Hmm, I
On Tue, 11 Oct 2011, Uros Bizjak wrote:
Hello!
Remove another orphan file from the testsuite directory.
2011-10-11 Uros Bizjak ubiz...@gmail.com
* lib/target-supports.exp (check_effective_target_fd_truncate):
Close and unlink test file before exit.
(can't quote
On Wed, 21 Sep 2011, Joey Ye wrote:
Committed in ARM/embedded-4_6-branch.
2011-09-21 Jiangning Liu jiangning@arm.com
Tune loop unrolling for cortex-m
* config/arm/arm-cores.def (cortex-m0): Change to new tune
cortex_v6m.
(cortex-m1): Likewise.
*
Date: Tue, 27 Sep 2011 19:23:22 +0200
From: Jan Hubicka hubi...@ucw.cz
this patch updates testsuite to cover both fat and slim LTO when linker plugin
is used and also both linker plugin and collect2 paths. I didn't wanted to
slow down testing too much so I just distributes the flags across
Date: Fri, 21 Oct 2011 00:19:32 +0200
From: Jan Hubicka hubi...@ucw.cz
Yes, if we scan assembler, we likely want -fno-fat-lto-objects.
then IIUC you need to patch *all* torture tests that use
scan-assembler and scan-assembler-not. Alternatively, patch
somewhere else, like not passing it
Date: Fri, 21 Oct 2011 17:44:15 +0200
From: Jan Hubicka hubi...@ucw.cz
I also noticed that tests scanning output of late optimization passes are
now getting UNRESOLVED state with slim LTO. We don't really lose coverage
here because we test fat LTO with the other compilation, but probably
Date: Fri, 21 Oct 2011 20:34:05 +0200
From: Jan Hubicka hubi...@ucw.cz
I guess we could make ipa-dump/rtl-dump/tree-dump scanning to disable fat lto
and introduce variants intended to scan late tree dumps and ipa execution
dumps...
Ok, sounds like a plan. Are there any such
1 - 100 of 1105 matches
Mail list logo
