On 10/29/2011 09:17 PM, Tom de Vries wrote:
> Richard,
>
> I have a tentative fix for PR50764.
>
> In the example from the test-case, -fsched2-use-superblocks moves an insn from
> block 4 to block 3.
>
>2
> bar
>|
> ---+-
>/ \
> *
My check-gcc runs are completely dominated by the time it takes to
test compile.exp=20001226-1.c
On sparc when compiling this function at -O1 the lowest hanging fruit
is some sillyness in reorg. It is trying to test a very specific
condition within a well contained code block, but the label scan
Dear Mikael,
I intend to work my way through your patches, starting this evening.
I'll give you feedback as I go along and will OK the whole package,
rather than bits. Is that alright with you?
Cheers
Paul
On Fri, Oct 28, 2011 at 1:29 AM, Mikael Morin wrote:
>
--
The knack of flying is le
Richard,
I have a fix for PR50878.
A simplified form of the problem from the test-case of the PR is shown in this
cfg. Block 12 has as direct dominator block 5.
5
/ \
/ \
* *
6 7
| |
| |
* *
8 9
\ /
\ /
On 10/30/2011 09:20 AM, Tom de Vries wrote:
> Richard,
>
> I have a fix for PR50878.
Sorry, with patch this time.
Thanks,
- Tom
>
> A simplified form of the problem from the test-case of the PR is shown in this
> cfg. Block 12 has as direct dominator block 5.
>
> 5
>/ \
>
On 28 October 2011 20:44, Jakub Jelinek wrote:
> Hi!
Hi,
>
> This patch implements what I've talked about, with this we can now
> with -mavx2 as well as -mxop vectorize long long/unsigned long long
> shifts by int or long long/unsigned long long shifts by long long
> (where the FE casts it to in
On Sat, Oct 29, 2011 at 2:36 AM, Maxim Kuvyrkov wrote:
> On 29/10/2011, at 1:57 AM, Richard Guenther wrote:
>
>>
>> We fail to keep the cannot-inline flag up-to-date when turning
>> indirect to direct calls. The following patch arranges to do
>> this during statement folding (which should always
On Sun, Oct 30, 2011 at 8:49 AM, David Miller wrote:
>
> My check-gcc runs are completely dominated by the time it takes to
> test compile.exp=20001226-1.c
>
> On sparc when compiling this function at -O1 the lowest hanging fruit
> is some sillyness in reorg. It is trying to test a very specific
On Sun, Oct 30, 2011 at 9:27 AM, Tom de Vries wrote:
> On 10/30/2011 09:20 AM, Tom de Vries wrote:
>> Richard,
>>
>> I have a fix for PR50878.
>
> Sorry, with patch this time.
Ok for now, but see Davids mail and the complexity issue with iteratively
updating dominators. It seems to me that we kn
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 Japanese team of translators. The file is available at:
http://translationproject.org/latest/gcc/ja.po
(This file, 'gcc-4.6.1.ja.po', has jus
On Sat, 2011-10-29 at 20:48 +0300, Ville Voutilainen wrote:
> >Could someone please review this?
>
> + if (cxx_dialect < cxx0x && !in_system_header)
> + pedwarn (input_location, OPT_pedantic,
> + "comma at end of enumerator list");
>
> Why not use maybe_warn_cpp0
On Fri, 4 Feb 2011, Michael Meissner wrote:
> After updating the mainline and 4.5 trees with the fix for PR
> target/47272 that restores vec_ld and vec_st to generate only Altivec
> memory instructions, I added the following to the documentation:
Here are some minor editorial changes I applied o
I see this was not applied, and also did not get any review comments.
Let me add our build system maintainers.
If something like this goes in, I suggest to avoid direct references
to SVN (which is a technical detail) and use something more generic
and spell GCC as opposed to gcc when it refers t
Installed based on a request by RMS.
Gerald
2011-10-25 Gerald Pfeifer
* NEWS (GCC 2.95): Refer to GNU/Linux instead of Linux.
(EGCS 1.0): Ditto.
Index: NEWS
===
--- NEWS(revision 180677)
+++ NEWS
Hello list, I updated this patch to latest trunk and also incorporated
apinski's suggestion to use stpcpy() instead of a custom loop.
Bootstrapped and tested again on i386, no regressions. The comments from
my previous email still apply, I never got a reply:
On Mon, 22 Aug 2011, Dimitrios Apos
Applied. Busy work on a foggy October afternoon...
Gerald
2011-10-30 Gerald Pfeifer
* faq.xml (Who's in charge of it?): Refer to the Linux kernel
instead of just Linux.
(How do I install libstdc++?): Refer to GNU/Linux instead of
just Linux.
Index: doc/xml/f
Add -fno-common to some more tests on hppa*-*-hpux* to avoid limited
alignment capabilities.
Tested on hppa2.0w-hp-hpux11.11. Committed to trunk.
Dave
--
J. David Anglin dave.ang...@nrc-cnrc.gc.ca
National Research Council of Canada (613) 990-0752 (
Hello!
2011-10-30 Uros Bizjak
* config/i386/i386.md (avx2_vec_dup): Macroize insn from
avx2_vec_dup{v8sf,v4sf} using VF1 mode iterator.
(vec_dupv4sf): Remove expander.
(vec_dupv4sf): Merge from *vec_dupv4sf and *vec_dupv4sf_avx.
(vec_dupv2df): Remove exp
At first this was only triggered by Linux vs GNU/Linux, but then I
noticed GCC being lower-cased and the Red Hat Linux reference when
we actually do not support that old version of glibc anymore at all.
Committed to mainline.
Gerald
2011-10-30 Gerald Pfeifer
* prerequisites.xml: Ref
On 30 October 2011 12:17, Magnus Fromreide wrote:
> Attached is a variation where maybe_warn_cpp0x is used.
> Please note how my new pedwarn breaks the pattern in maybe_warn_cpp0x.
Looks reasonable to me, but I'm not a maintainer. :) Jason?
Ping? I believe I have addressed all the reviewer's (namely Joseph Myers')
comments to date.
Thanks,
Walter Lee
Greetings,
IVOPTS handles strength reduction of induction variables, but GCC does
not currently perform strength reduction in straight-line code. This
has been noted before in PR22586 and PR35308. PR46556 is also a case
that could be handled with strength reduction. This patch adds a pass
to pe
Ping.
On Mon, 2011-10-24 at 08:38 -0500, William J. Schmidt wrote:
> OK, I've removed the pointer-arithmetic case from expand, to be handled
> later by straight-line strength reduction. Here's the patch to deal
> with just the specific pattern of PR46556 (which will also eventually be
> handled b
On 30 October 2011 15:36, Gerald Pfeifer wrote:
> At first this was only triggered by Linux vs GNU/Linux, but then I
> noticed GCC being lower-cased and the Red Hat Linux reference when
> we actually do not support that old version of glibc anymore at all.
Are those instructions not valid for Fedo
On Sat, 29 Oct 2011, Richard Guenther wrote:
> I tried to look at what we get for -fno-pic vs. -fpic and -fno-pic is
> completely
> dropped from the decoded options list (not sure what happens on targets
> with -fpic as default). So it seems at most one state (the non-default one)
> survives her
On 10/27/2011 03:47 PM, Jason Merrill wrote:
On 10/27/2011 03:32 PM, Ed Smith-Rowland wrote:
+ if (TREE_CODE (TREE_TYPE (decl)) != LANG_TYPE)
+argtypes = TYPE_ARG_TYPES (TREE_TYPE (decl));
If you have multiple overloaded operator"" _foo, you need to iterate
over them looking for the one
On Sun, 30 Oct 2011, Jonathan Wakely wrote:
> Are those instructions not valid for Fedora though? And RHEL?
Anything using "rpm -e --nodeps" is not valid anywhere, I'd claim.
And "rpm -i --define "_install_langs all" glibc-common-2.2.5-34.i386.rpm"
definitely won't work on anything released in t
Hi,
thus I'm working on a new warning for 0 as null ptr constant, which
should be useful for people moving to C++11' nullptr. Looks like a good
place to check for that is cp_convert_to_pointer, then the difficulty is
coping correctly with things like:
int* p;
if (p)
;
where c
On 30 October 2011 17:16, Gerald Pfeifer wrote:
> I hope this addresses your questions?
It certainly does - thanks.
On Sun, 17 Apr 2011, Axel Freyn wrote:
> I propose to add a phrase to the "rpath"-section (Dynamic linker is
> unable to find GCC libraries), which explains how to use "-R" as
> compiler-option (by using "-Wl,")
This is a good idea, thank you. I applied the small variation of
your original patch
On Sunday 30 October 2011 09:16:09 Paul Richard Thomas wrote:
> Dear Mikael,
>
> I intend to work my way through your patches, starting this evening.
> I'll give you feedback as I go along and will OK the whole package,
> rather than bits. Is that alright with you?
Sure.
Mikael
While looking into Axel Freyn's suggestion, I noticed how that
answer really is too long winded. This cuts down things quite
a bit, making this more digestable hopefully.
Applied.
Gerald
Index: faq.html
===
RCS file: /cvs/gcc/wwwdo
On Tuesday 25 October 2011 07:39:44 Thomas Koenig wrote:
> Ping ** 0.571428
>
Let's keep Jakub CC-ed for mixes of OpenMP and frontend optimizations. ;-)
There are two commented lines in the testcase. Is it expected?
Otherwise doesn't look too bad...
Mikael
> > Jakub Jelinek wrote:
> >> Though,
This patch breaks bootstrap on AIX because it includes
before "config.h". "config.h" header can affect system headers. I am
not sure why stdio.h should be included because system.h itself
includes . The appended patch moves stdio.h after config.h,
but maybe gcc-ar.h should not include stdio.h e
On Mon, 14 Jun 2010, Dave Korn wrote:
> * htdocs/gcc-4.5/changes.html: Remove explicit mentions of ELF
> format from LTO documentation.
Ouch, I noticed this patch of yours never was applied, perhaps
some misunderstanding between Richi and you (him assuming you'd
go ahead and you waitin
On Fri, Oct 28, 2011 at 4:48 PM, Diego Novillo wrote:
> Isn't this the same patch as
> http://gcc.gnu.org/ml/gcc-patches/2011-10/msg02348.html?
No, it's updated to do exactly what we do now. Changes to behavior to be split
to 3/n (like warning about mismatches or fixing the way we handle fPIC).
On Sun, Oct 30, 2011 at 9:39 PM, David Edelsohn wrote:
> This patch breaks bootstrap on AIX because it includes
> before "config.h". "config.h" header can affect system headers. I am
> not sure why stdio.h should be included because system.h itself
> includes . The appended patch moves stdio.h
On Fri, Oct 28, 2011 at 07:43:58AM +0200, Tobias Burnus wrote:
> Am 28.10.2011 01:27, schrieb Steve Kargl:
> >The attached patch tightens the checking of the arguments
> >of the dshiftl and dshiftr argument. It also does a kind
> >type conversion when either I or J is a BOZ to the kind
> >type of
This factors the computation of mangled names so it can be called
without actually setting the assembler name on the DECL. It is used
in the pph branch for merging symbols that are replicated in multiple
images.
On trunk, it changes nothing, but it sets it up for when we are ready
to merge the p
I found this on the PPH branch. We were not handling TYPE_ADDR_SPACE
in the streamer.
Fixed with this patch. Richi, I will apply it on trunk unless you
remember some reason why we never streamed this? It does not seem to
affect any LTO tests.
Tested with lto profiledbootstrap on x86_64.
Die
Where there can be multiple things wrong with a pattern sequence,
performance-wise, and multiple things might be fixed up, depending
on factors like available registers, providing patterns for every
combination leads to combinatorial explosion.
It is simpler to describe the available transformatio
I've committed the following small whitespace patch
that allows one to do 'grep -E ^gfc_free' to find
functions starting with this pattern.
2011-10-30 Steven G. Kargl
* symbol.c (gfc_free_charlen): Whitespace.
Index: symbol.c
=
Mikael Morin wrote:
Let's keep Jakub CC-ed for mixes of OpenMP and frontend optimizations. ;-)
There are two commented lines in the testcase. Is it expected?
Otherwise doesn't look too bad...
I had also a glance at the patch - and it looks reasonable; in
particular, I failed to generate a fai
I've had this patch in my i386-*-freebsd and x86_64-*-freebsd
for more than a week. Several 'gmake check-gfortran' have
been run during that time without a regression.
OK for trunk?
2011-10-30 Steven G. Kargl
PR fortran/50404
* io.c (gfc_resolve_close): A CLOSE statement req
Tests such as limits-fndefn.c spend %97 of their time in
next_real_insn() when -g is on the command line.
It's the invocation from dwarf2out_var_location(). These test cases
are basically 100,000 consecutive var location notes, followed by a
real instruction.
This is similar to the reorg issue
On 10/30/2011 07:50 PM, Steve Kargl wrote:
I've had this patch in my i386-*-freebsd and x86_64-*-freebsd
for more than a week. Several 'gmake check-gfortran' have
been run during that time without a regression.
OK for trunk?
OK, thanks for patch.
Jerry
... this is another option: use an 'integer_zero_or_nullptr_node (tree)'
defined differently for C and C++. Certainly the whole thing becomes
smaller.
Paolo.
Index: c-family/c.opt
===
--- c-family/c.opt (revi
OK.
Jason
Here's my start at adjusting things to use the C++11 name; feel free to
run with it.
Looking at it again, I think adding __GXX_EXPERIMENTAL_CXX11__ is a
mistake, we should just set __cplusplus to the C++11 value.
Jason
commit 9c331b6de02e796fa25b04ed206b8570c83ee237
Author: Jason Merrill
Dat
Have not done with reviewing. This is the first batch.
David
http://codereview.appspot.com/5303083/diff/1/gcc/passes.c
File gcc/passes.c (right):
http://codereview.appspot.com/5303083/diff/1/gcc/passes.c#newcode1423
gcc/passes.c:1423: NEXT_PASS (pass_tsan);
Move this to the same place as asan.
There is definitely more than can be done in this area, but at least
this is a start.
Next we can start trying to use the ASI_FL{8,16,32}_P short floating
point loads which zero extend a 8, 16, or 32 bit integer value into a
double precision float register.
gcc/
* config/sparc/sparc.c (
51 matches
Mail list logo
