On Fri, Aug 26, 2011 at 1:11 AM, H.J. Lu wrote:
> should support all Intel intrinsics. This patch adds
> BMI, BMI2 and LZCNT support to . OK for trunk?
OK if passes regression testing.
Uros.
Allocatable coarrays are freed and deregistered via the libcaf function
_gfortran_caf_deregister. Currently, the front end does not generate
calls to the that function, however, this patch already implements the
function.
See http://gcc.gnu.org/wiki/CoarrayLib and
http://gcc.gnu.org/ml/fortra
On 11-08-25 18:56 , Gabriel Charette wrote:
XPASS: g++.dg/pph/x7rtti.cc -fno-dwarf2-cfi-asm -fpph-map=pph.map -I.
(test for bogus messages, line )
> [ ... ]
Oops, my fault. When I changed x7rtti.cc into an executable test, I
altered line numbers and forgot to update the dg markers. Fixed
On Thu, Aug 25, 2011 at 5:37 PM, Sriraman Tallam wrote:
> Hi,
>
> Thanks for all the comments. I am attaching a new patch
> incorporating all of the changes mentioned, mainly :
>
> 1) Make __cpu_indicator_init a constructor in libgcc and guard to call
> it only once.
This is unreliable and you d
Hi,
We received this from Intel and would like to check in the trunk.
Could the maintainers of gcc/config take a look?
Thanks.
-Doug
2011-08-25 Mark D Horn
config/linux-android.h (ANDROID_STARTFILE_SPEC, ANDROID_ENDFILE_SPEC):
Add missing crt*.o objects for shared buildi
Hi,
Thanks for all the comments. I am attaching a new patch
incorporating all of the changes mentioned, mainly :
1) Make __cpu_indicator_init a constructor in libgcc and guard to call
it only once.
2) Add symbol versions.
3) Move all builtins to the i386 port.
4) Add check for atom processor.
5
Bound_method_expression in the Go frontend IR represents a method bound
to an object, as in v.m. The IR was permitting the method to be any
expression. However, Go does not support method pointers, so m was
always a specific method (Go supports a comparable but different
approach, method expressi
Hi,
should support all Intel intrinsics. This patch adds
BMI, BMI2 and LZCNT support to . OK for trunk?
Thanks.
H.J.
---
2011-08-25 H.J. Lu
* config/i386/bmi2intrin.h: Allow in .
* config/i386/bmiintrin.h: Likewise.
* config/i386/lzcntintrin.h: Likewise.
I'm getting the following pph test failure output after this patch
(I'll commit my patch on top of it anyways as I get the same errors
with a clean build and with my patch, which itself had a clean test
output before this recent pull before my commit).
XPASS: g++.dg/pph/x7rtti.cc -fno-dwarf2-cfi-a
Hi!
As the following testcase shows, if the last expression in statement
expression is array, mark_exp_read wasn't called on it.
Fixed thusly, bootstrapped/regtested on x86_64-linux and i686-linux,
ok for trunk/4.6?
2011-08-26 Jakub Jelinek
PR c/50179
* c-typeck.c (c_process_e
To prevent PPH images from depend on the context in which they were
generated, we require that the header file be compiled in isolation
and when included, it should only be included in the global context.
That is, things like
namespace Foo {
#include "bar.h"
...
};
should prevent bar.h f
On 07/18/11 18:47, Vladimir Makarov wrote:
> But I guess comb-vector is popular for a reason. We could tolerate slow
> compression time because it is done once but worse compression and
> slower access would have a really bad impact on the compiler time.
With some fixes that I need to make to the
On Thu, Aug 25, 2011 at 18:14, Gabriel Charette wrote:
> This was the last thing remaining on my cleanup list.
>
> As suggested by Steven and Jason in issue4550121, we should use
> REAL_IDENTIFIER_TYPE_VALUE for IDENTIFIER_NODEs instead of TREE_TYPE
> (although the former resolves to the later i
This was the last thing remaining on my cleanup list.
As suggested by Steven and Jason in issue4550121, we should use
REAL_IDENTIFIER_TYPE_VALUE for IDENTIFIER_NODEs instead of TREE_TYPE (although
the former resolves to the later in its macro definition, this is more robust
to potential later c
On Aug 25, 2011, at 1:35 PM, Michael Meissner wrote:
> The alternative is something like what Kenney and Mike are doing in their
> private port, where they have new syntax in the MD file for builtins.
I think the issue is actually largely orthogonal. In our code, we generate
which code is used b
During determining the intent of variable I run into problems with PHI nodes.
The problematical GIMPLE code looks:
# BLOCK 196
# PRED: 194 (false)
(...)
ndycD.8665_1099 = 1;
# BLOCK 197
# PRED: 196 (true) 207 (false)
# ndycD.8665_4 = PHI
(...)
# BLOC
On Wed, Aug 24, 2011 at 11:06:55AM +0200, Richard Guenther wrote:
> This basically would make DECL_BUILT_IN_CLASS no longer necessary
> if all targets where converted, right? (We don't currently have any
> BUILT_IN_FRONTEND builtins). That would sound appealing if this
> patch weren't a partial t
Mateusz Grabowski wrote:
>
>
>
If a function calls another, the intent of variables should be passed to the
first one. But what if the callee is in the other compilation unit? Does
anyone have knowledge of using LTO mode?
>
>
At this moment I have many compilation units. In my case the m
On Thu, 25 Aug 2011, Ramana Radhakrishnan wrote:
> On 25 August 2011 18:31, Julian Brown wrote:
> > On Thu, 25 Aug 2011 16:46:50 +0100
> > Julian Brown wrote:
> >
> >> So, OK to apply this version, assuming testing comes out OK? (And the
> >> followup patch [2/2], which remains unchanged?)
> >
>
On 25 August 2011 18:31, Julian Brown wrote:
> On Thu, 25 Aug 2011 16:46:50 +0100
> Julian Brown wrote:
>
>> So, OK to apply this version, assuming testing comes out OK? (And the
>> followup patch [2/2], which remains unchanged?)
>
> FWIW, all tests pass, apart from gcc.target/arm/volatile-bitfie
Recently I sent the patch which was mostly a caller-saves subpass
rewriting. It resulted in removing a call df-analyze because the new
subpass does not use DF-infrastructure as all subsequent subpasses.
Before caller-saves subpass there is a small subpass which
substitutes scratches to pseu
These are both REG_ARGS_SIZE mis-match problems.
The 49864 problem is caused by cross-jumping doing the wrong
thing. The 50132 problem is caused by fixup_args_size_notes
think-o where we failed to properly handle pops.
Techinically I should have split these changes apart, but I
tested them toget
Hello!
As noted in the PR, we also have to protect conversion from
round->lround for non-TARGET_C99_FUNCTIONS targets. Otherwise, gcc
chokes in fold_fixed_mathfn, trying to canonicalize iround to
(non-existent) lround. It looks to me, that we can trigger the same
problem trying to convert (long lo
* g++.dg/pph/x7rtti.cc: Make it executable.
diff --git a/gcc/testsuite/g++.dg/pph/x7rtti.cc
b/gcc/testsuite/g++.dg/pph/x7rtti.cc
index 297ebe2..0da2f97 100644
--- a/gcc/testsuite/g++.dg/pph/x7rtti.cc
+++ b/gcc/testsuite/g++.dg/pph/x7rtti.cc
@@ -1,3 +1,4 @@
+// { dg-do run }
// { dg-xfa
Hi,
> here's the updated version of the patch.
>
> The goal is to remove the 'i' iterator from the following example, by
> replacing 'i < n' with 'p < base + n'.
>
> void
> f (char *base, unsigned long int i, unsigned long int n)
> {
> char *p = base + i;
> do
> {
> *p = '\0';
>
On 08/25/2011 02:07 PM, Richard Sandiford wrote:
Vladimir Makarov writes:
On 08/25/2011 05:57 AM, Richard Sandiford wrote:
Vladimir Makarov writes:
Instead of using explicitly necessary number of registers, I used
contains_reg_of_mode which also checks the number of necessary registers
On Thu, Aug 25, 2011 at 8:00 PM, Richard Henderson wrote:
>> @@ -3445,7 +3463,7 @@
>> })
>>
>> (define_insn "*zero_extendsidi2_rex64"
>> - [(set (match_operand:DI 0 "nonimmediate_operand"
>> "=r,o,?*Ym,?*y,?*Yi,*Y2")
>> + [(set (match_operand:DI 0 "nonimmediate_operand" "=r,o,?*Ym,?*y,?*Yi,
On 08/24/11 13:12, Richard Sandiford wrote:
> Sorry, I'm find this a bit tough to review. Could you provide some
> overview comments somewhere to say what the new algorithm is?
> The comment at the head of regrename.c still describes the current
> bb-local algorithm.
New patch below, with extra c
We weren't protecting all errors in convert_like_real with a complain
check. So this patch adds one at the top of the file to handle all
bad_p cases. The second patch then removes various checks in the rest
of the function that are now redundant.
Tested x86_64-pc-linux-gnu, applying to trunk
progmem_section is a section to put jump tables in.
This patch puts jump tables in individual sections if
-ffunction-section is on and does some more cleanup around
that, i.e. implement TARGET_ASM_FUNCTION_RODATA_SECTION hook.
progmem_section is renamed to progmem_swtable_section and is
local to
Vladimir Makarov writes:
> On 08/25/2011 05:57 AM, Richard Sandiford wrote:
>> Vladimir Makarov writes:
>>> Instead of using explicitly necessary number of registers, I used
>>> contains_reg_of_mode which also checks the number of necessary registers
>>> but also it checks that the register c
> @@ -3445,7 +3463,7 @@
> })
>
> (define_insn "*zero_extendsidi2_rex64"
> - [(set (match_operand:DI 0 "nonimmediate_operand" "=r,o,?*Ym,?*y,?*Yi,*Y2")
> + [(set (match_operand:DI 0 "nonimmediate_operand" "=r,o,?*Ym,?*y,?*Yi,*x")
> (zero_extend:DI
>(match_operand:SI 1 "nonimmed
Julian Brown writes:
> On Wed, 24 Aug 2011 17:04:55 +0100
> Julian Brown wrote:
>
>> On Sun, 07 Aug 2011 18:47:57 +0100
>> Richard Sandiford wrote:
>>
>> > This patch caused several regressions on big-endian 64-bit MIPS
>> > targets, which now try to shift single-precision floating-point
>> > a
On Thu, Aug 25, 2011 at 13:17, Gabriel Charette wrote:
> What do you mean? the || is aligned with the 'marker' entry above it.
> Do you want the || to be aligned? i.e.
> marker == PPH_RECORD_IREF
> || marker == PPH_RECORD_XREF
> || marker == PPH_RECORD_PREF
> ?
Yeah, this way. Every operand of
This patch fixes the x1key* tests by changing the way we register
functions to the middle end in the reader.
We were calling expand_or_defer_fn, but that was re-computing tree
attributes that we had already computed and, worse, it was assuming
parser context in scope_chain that the reader did not
On Thu, 25 Aug 2011 16:46:50 +0100
Julian Brown wrote:
> So, OK to apply this version, assuming testing comes out OK? (And the
> followup patch [2/2], which remains unchanged?)
FWIW, all tests pass, apart from gcc.target/arm/volatile-bitfields-3.c,
which regresses. The output contains:
Removing useless slashes in path to avoid issues when RPM extracts debug
informations.
---
contrib/ChangeLog.MELT |3 +++
contrib/MELT-Plugin-Makefile | 30 +++---
gcc/ChangeLog.MELT |3 +++
gcc/melt-module.mk |8
4 files ch
Hello,
There are some points in MELT build where several slashes are used and
present in paths, mainly when calling GCC. This is bad not only for
cosmetic reasons, but it also makes rpm not happy when extracting debug
symbols. The following patch fixes this.
On 08/25/2011 05:57 AM, Richard Sandiford wrote:
Vladimir Makarov writes:
Instead of using explicitly necessary number of registers, I used
contains_reg_of_mode which also checks the number of necessary registers
but also it checks that the register class can hold value of given
mode. This
On Monday 22 August 2011 23:22:08 Tobias Burnus wrote:
> Dear all,
>
> this patch added token/offset support for assumed-shape coarray dummies
> (with .-fcoarray=lib).
>
> Build and regtested.
> OK for the trunk?
>
OK, thanks.
Mikael
On Wednesday 24 August 2011 15:31:17 Tobias Burnus wrote:
> > Isn't there some rules about backporting? The way we do it now, it
> > looks completely arbitrary.
>
> I think it *is* arbitrary - and unavoidable so.
>
> The main idea behind regression fixing is to make sure that what once
> worked s
On Thu, Aug 25, 2011 at 6:49 AM, Ramana Radhakrishnan
wrote:
> I know this is intended for the google branches but shouldn't such a
> change be in the x86_64 backend rather than such a general change to
> params.def .
I wouldn't consider this a backend-specific change. The parameter
generally af
Hi Richard,
thanks for the review.
On 08/25/2011 12:45 PM, Richard Guenther wrote:
> On Thu, Aug 25, 2011 at 12:32 PM, Tom de Vries wrote:
>> Jakub,
>>
>> This patch fixes a segmentation violation, which occurs when printing a
>> MEM_REF
>> or COMPONENT_REF containing a released ssa name. This
On Mon, 4 Jul 2011 13:43:31 +0200 (CEST)
"Ulrich Weigand" wrote:
> Julian Brown wrote:
>
> > The most awkward change in the patch is to generic code (expmed.c,
> > {store,extract}_bit_field_1): in big-endian mode, the existing
> > behaviour (when inserting/extracting a bitfield to a memory
> > l
Am 25.08.2011 16:39, schrieb Tobias Burnus:
Scalar coarray components didn't use the array descriptor, which caused
all kinds of ICEs.
Fix by this relatively simple patch.
OK for the trunk?
OK (bordering on obvious, although I'm not sure which side of the border :-)
Thanks for the patch!
Hello Richard and Mike,
Thank you for your interest in the cilkplus branch to GCC 4.7.
While the full Intel Cilk Plus Specification (available at
http://software.intel.com/en-us/articles/intel-cilk-plus-specification/)
includes array notations, they are not implemented in the current rel
Hello,
The texi file defining the MELT Plugin API was missing the
versionsubtitle macro definition (which is however present in
meltplugin.texi), and this resulted in PDF documentation generation
failing. Following patch fixes this by adding the macro to
meltpluginapi.texi.
The MELT Plugin API texi source misses the macro versionsubtitle which
is also defined in meltplugin.texi. This commit simply steals the
definition from the last one.
---
contrib/ChangeLog.MELT |3 +++
contrib/meltpluginapi.texi | 10 ++
2 files changed, 13 insertions(+), 0 dele
Scalar coarray components didn't use the array descriptor, which caused
all kinds of ICEs.
Fix by this relatively simple patch.
OK for the trunk?
* * *
Pending coarray patch for -fcoarray=lib: Add support for assumed-shape
coarray dummies (passing offset and token); see
http://gcc.gnu.org/m
Tom> Any comments on this?
Tom> I'd like to get it in; Phil found a bug in the std::tuple printer, and
Tom> it would be nice to put in a test case along with the fix.
Benjamin> Hey Tom (and Phil!).
Benjamin> Sorry for the delay: this looks fine. Please put it in on trunk and
Benjamin> enjoy your
Plugin documentation was being built as .info file thanks to the
default's make .info target, but none were defined for HTML and PDF. The
present commit add the missing targets.
---
contrib/ChangeLog.MELT |3 +++
contrib/MELT-Plugin-Makefile |9 +
2 files changed, 12 inserti
Hello,
Documentation for the MELT plugin was only produced as .info file, but
the PDF and HTML output were missing. This was due to missing target for
both ; hence the following patch which fixes by defining two targets:
- %.html
- %.pdf
Simply calling respectivement $(TEXI2HTML) and $(TEXI2PDF)
Path computation for installation in GCC's plugin/melt-modules/ path was
broken (in fact not updated to the latest changes). Present commit fixes
this by reading the link targets and installing them.
---
contrib/ChangeLog.MELT |2 ++
contrib/MELT-Plugin-Makefile | 10 +-
2 fil
Hello,
Thanks for your suggestions. I made the suggested changes, I hope it
matches your requirements :).
On Thu, Aug 25, 2011 at 3:15 PM, Artem Shinkarov
wrote:
> On Thu, Aug 25, 2011 at 2:00 PM, Richard Guenther
> wrote:
>> On Thu, Aug 25, 2011 at 2:45 PM, Artem Shinkarov
>> wrote:
>>> On Thu, Aug 25, 2011 at 12:39 PM, Richard Guenther
>>> wrote:
On Thu, Aug 25, 2011 at 1:07 PM, Artem Shinka
On 08/24/11 13:12, Richard Sandiford wrote:
> Sorry, I'm find this a bit tough to review. Could you provide some
> overview comments somewhere to say what the new algorithm is?
Will resubmit. To make the patch smaller next time, I've committed the
following as obvious (BSRT i686-linux).
Bernd
I
On 24 August 2011 22:43, Mark Heffernan wrote:
> This patch bumps up the parameter 'hot-bb-count-fraction' from 1
> to 4. This results in about a 0.5% geomean performance
> improvement across internal benchmarks for x86-64 LIPO. The parameter
> change effectively increases the number of
* Alexandre Lissy wrote on Thu, Aug 25, 2011 at 03:26:46PM CEST:
> Path computation for installation in GCC's plugin/melt-modules/ path was
> broken (in fact not updated to the latest changes). Present commit fixes
> this by reading the link targets and installing them.
> --- a/contrib/MELT-Plugin
> -Original Message-
> From: Georg-Johann Lay [mailto:a...@gjlay.de]
> Sent: Thursday, August 25, 2011 7:31 AM
> To: gcc-patches@gcc.gnu.org
> Cc: Denis Chertykov; Weddington, Eric
> Subject: Re: [Patch,AVR]: Bit of Cleanup [3/3]: Remove
> byte_immediate_operand
>
> Georg-Johann Lay wrot
> -Original Message-
> From: Georg-Johann Lay [mailto:a...@gjlay.de]
> Sent: Thursday, August 25, 2011 7:30 AM
> To: gcc-patches@gcc.gnu.org
> Cc: Denis Chertykov; Weddington, Eric
> Subject: Re: [Patch,AVR]: Bit of Cleanup [2/3]: Let avr_regno_reg_class
> return smallest class
>
> Georg
> -Original Message-
> From: Georg-Johann Lay [mailto:a...@gjlay.de]
> Sent: Thursday, August 25, 2011 7:28 AM
> To: gcc-patches@gcc.gnu.org
> Cc: Denis Chertykov; Weddington, Eric
> Subject: Re: [Patch,AVR]: Bit of Cleanup [1/3]: Test string for prefix
>
> Georg-Johann Lay wrote:
> > Th
Georg-Johann Lay wrote:
> These are three small patches to clean up the avr BE a bit:
>
> #1: Use custom macro to test of a string starts with given prefix
>
> #2: Let avr_regno_reg_class return smallest register class
>
> #3: Replace/remove superfluous byte_immediate_operand and some protos.
>
Georg-Johann Lay wrote:
> These are three small patches to clean up the avr BE a bit:
>
> #1: Use custom macro to test of a string starts with given prefix
>
> #2: Let avr_regno_reg_class return smallest register class
>
> #3: Replace/remove superfluous byte_immediate_operand and some protos.
>
Georg-Johann Lay wrote:
> These are three small patches to clean up the avr BE a bit:
>
> #1: Use custom macro to test of a string starts with given prefix
>
> #2: Let avr_regno_reg_class return smallest register class
>
> #3: Replace/remove superfluous byte_immediate_operand and some protos.
>
Path computation for installation in GCC's plugin/melt-modules/ path was
broken (in fact not updated to the latest changes). Present commit fixes
this by reading the link targets and installing them.
---
contrib/ChangeLog.MELT |2 ++
contrib/MELT-Plugin-Makefile |8 +++-
2 files
Hello,
Changes recently happened on the MELT modules which broke the way the
install-melt-modules target in MELT's Makefile in the plugin case works.
Attached is a patch that fixes this.
These are three small patches to clean up the avr BE a bit:
#1: Use custom macro to test of a string starts with given prefix
#2: Let avr_regno_reg_class return smallest register class
#3: Replace/remove superfluous byte_immediate_operand and some protos.
All patches tested without regression.
This patch restores gcc.dg/Wshadow-3.c which was overwritten by
r148442. I noticed this by the strange test name for a test
checking -Warray-bounds warnings ...
Committed. (reversed patch below)
Richard.
2011-08-25 Richard Guenther
* gcc.dg/Wshadow-3.c: Restore original content de
On Thu, Aug 25, 2011 at 2:00 PM, Richard Guenther
wrote:
> On Thu, Aug 25, 2011 at 2:45 PM, Artem Shinkarov
> wrote:
>> On Thu, Aug 25, 2011 at 12:39 PM, Richard Guenther
>> wrote:
>>> On Thu, Aug 25, 2011 at 1:07 PM, Artem Shinkarov
>>> wrote:
On Thu, Aug 25, 2011 at 11:09 AM, Richard Gue
On Thu, Aug 25, 2011 at 2:45 PM, Artem Shinkarov
wrote:
> On Thu, Aug 25, 2011 at 12:39 PM, Richard Guenther
> wrote:
>> On Thu, Aug 25, 2011 at 1:07 PM, Artem Shinkarov
>> wrote:
>>> On Thu, Aug 25, 2011 at 11:09 AM, Richard Guenther
>>> wrote:
On Thu, Aug 25, 2011 at 8:20 AM, Artem Shink
On Thu, Aug 25, 2011 at 12:39 PM, Richard Guenther
wrote:
> On Thu, Aug 25, 2011 at 1:07 PM, Artem Shinkarov
> wrote:
>> On Thu, Aug 25, 2011 at 11:09 AM, Richard Guenther
>> wrote:
>>> On Thu, Aug 25, 2011 at 8:20 AM, Artem Shinkarov
>>> wrote:
Here is a cleaned-up patch without the hook.
On Wed, Aug 24, 2011 at 9:32 PM, Alan Modra wrote:
> Wouldn't -Wshadow be more useful if it obeyed -Wno-system-headers?
> For code like
>
> #include
> int foo (int atof);
> int foo (int atof) { return atof; }
>
> we currently do not warn on the prototype, but do on the functi
OK with a couple of nits below.
Diego.
http://codereview.appspot.com/4956041/diff/1/gcc/cp/pph-streamer-in.c
File gcc/cp/pph-streamer-in.c (right):
http://codereview.appspot.com/4956041/diff/1/gcc/cp/pph-streamer-in.c#newcode155
gcc/cp/pph-streamer-in.c:155: || marker == PPH_RECORD_PREF;
154
This patch causes regression in one of the Spec2000 benchmarks on
arm-none-linux-gnueabi cortex-a9.
The benchmark 173.applu from CFP2000 dropped performance by about 8% between
revisions 177367 and 177368. Other benchmarks are not affected.
In the assembly generated by the new version, the two m
Several nodes were not present in the menu, fixing. Thanks to Patrice
Dumas .
---
contrib/meltpluginapi.texi |3 +++
gcc/ChangeLog.MELT |4
2 files changed, 7 insertions(+), 0 deletions(-)
diff --git a/contrib/meltpluginapi.texi b/contrib/meltpluginapi.texi
index b2d843f..b7
Hello,
A couple of nodes in the texi file for the MELT Plugin API were not
present in the menu, hence makeinfo failed. Fixing with help from
Patrice Dumas .
The meltgendoc.texi target runs GCC and might return a value of 1 which
confuses make while the texi file was correctly generated ; thus, adding
'|| true' allows for the build to continue instead of stopping.
---
gcc/ChangeLog.MELT |4
gcc/melt-build.tpl |2 +-
2 files changed, 5 ins
Hello,
The meltgendoc.texi target can "fail", returning a value of 1 while the
file has been correctly written. The attached patch allows to circumvent
this.
On 08/25/2011 01:42 PM, Tom de Vries wrote:
> Hi Zdenek,
>
> here's the updated version of the patch.
>
> The goal is to remove the 'i' iterator from the following example, by
> replacing 'i < n' with 'p < base + n'.
>
> void
> f (char *base, unsigned long int i, unsigned long int n)
> {
> cha
Hello,
I think it is useful to run this case for newer arm targets. So the patch
intends to skip the warning of architecture conflicts. Is it ok to commit to
trunk?
BR,
Terry
gcc/testsuite/ChangeLog:
2011-08-25 Terry Guo
* gcc.dg/tls/pr42894.c: Add dg-prune-output to skip
ar
Hi Zdenek,
here's the updated version of the patch.
The goal is to remove the 'i' iterator from the following example, by
replacing 'i < n' with 'p < base + n'.
void
f (char *base, unsigned long int i, unsigned long int n)
{
char *p = base + i;
do
{
*p = '\0';
p++;
i++;
On Thu, Aug 25, 2011 at 1:07 PM, Artem Shinkarov
wrote:
> On Thu, Aug 25, 2011 at 11:09 AM, Richard Guenther
> wrote:
>> On Thu, Aug 25, 2011 at 8:20 AM, Artem Shinkarov
>> wrote:
>>> Here is a cleaned-up patch without the hook. Mostly it works in a way
>>> we discussed.
>>>
>>> So I think it is
Hello!
Modernize i386 md files by using "enabled" attribute instead of Y2, Y3
and Y4 conditional register constraints. I will investigate other
conditional register constraints as well.
2011-08-25 Uros Bizjak
* config/i386/i386.md (isa): Add sse2, sse2_noavx, sse3,
sse4 and ss
On Thu, Aug 25, 2011 at 11:09 AM, Richard Guenther
wrote:
> On Thu, Aug 25, 2011 at 8:20 AM, Artem Shinkarov
> wrote:
>> Here is a cleaned-up patch without the hook. Mostly it works in a way
>> we discussed.
>>
>> So I think it is a right time to do something about vcond patterns,
>> which would
Fixed.
Changelog:
2011-08-25 Ilya Tocar
* config/i386/fmaintrin.h: New.
* config.gcc: Add fmaintrin.h.
* config/i386/i386.c
(enum ix86_builtins) : New.
: Likewise.
* config/i386/sse.md (fmai_vmfmadd_): New.
On Thu, Aug 25, 2011 at 02:47:51PM +0400, Ilya Tocar wrote:
> Sorry. Like this?
No.
> * gcc.target/i386/sse-12.c: Add -mfma.
> * gcc.target/i386/sse-13.c: Likewise.
> * gcc.target/i386/sse-14.c: Likewise.
> * gcc.target/i386/sse-22.c: Likewise.
>
Sorry. Like this?
Changelog:
2011-08-25 Ilya Tocar
* config/i386/fmaintrin.h: New.
* config.gcc: Add fmaintrin.h.
* config/i386/i386.c
(enum ix86_builtins) : New.
: Likewise.
* config/i386/sse.md (fmai_vmfmadd_): Ne
On Thu, Aug 25, 2011 at 12:32 PM, Tom de Vries wrote:
> Jakub,
>
> This patch fixes a segmentation violation, which occurs when printing a
> MEM_REF
> or COMPONENT_REF containing a released ssa name. This can happen when we
> print
> basic blocks upon removal, enabled by -ftree-dump-tree-*-deta
Jakub,
This patch fixes a segmentation violation, which occurs when printing a MEM_REF
or COMPONENT_REF containing a released ssa name. This can happen when we print
basic blocks upon removal, enabled by -ftree-dump-tree-*-details (see
remove_bb:tree-cfg.c).
Bootstrapped and reg-tested on x86_64
Hello,
A prevoous commit introduced a typo on the output argument when generating
documentation, hence the attached commit fixes the issue.
A previous commit has introduced a change for melt output argument in
meltgendoc.texi target: going from $@ ti $(basename $@). This is bad
since we are loosing the extension of the filename, hence the build
process is stopped because of missing meltgendoc.texi file.
---
gcc/ChangeLog.MELT |4
On Thu, Aug 25, 2011 at 8:20 AM, Artem Shinkarov
wrote:
> Here is a cleaned-up patch without the hook. Mostly it works in a way
> we discussed.
>
> So I think it is a right time to do something about vcond patterns,
> which would allow me to get rid of conversions that I need to put all
> over the
Vladimir Makarov writes:
>Instead of using explicitly necessary number of registers, I used
> contains_reg_of_mode which also checks the number of necessary registers
> but also it checks that the register class can hold value of given
> mode. This resulted in different register pressure c
Hello,
Following is a patch that fixes usage of the now invalid 'static' flavor
and replaces its usage with 'quicklybuilt'.>From 546c86cd45114470da4cb7811c71f1fcde48714b Mon Sep 17 00:00:00 2001
From: Alexandre Lissy
Date: Thu, 25 Aug 2011 11:26:54 +0200
Subject: [PATCH] [MELT] Fix bad flavor sta
On Thu, Aug 25, 2011 at 10:18 AM, Ilya Tocar wrote:
> Changelog:
>
> 2011-08-25 Ilya Tocar
>
> * config/i386/fmaintrin.h: New.
> * config.gcc: Add fmaintrin.h.
> * config/i386/i386.c
> * (IX86_BUILTIN_VFMADDSS3): New.
> (IX8
On Wed, 24 Aug 2011, Richard Guenther wrote:
> On Fri, 19 Aug 2011, Richard Guenther wrote:
>
> > On Fri, 19 Aug 2011, Eric Botcazou wrote:
> >
> > > > Looking at the Ada case I believe this happens because
> > > > Ada has negative DECL_FIELD_OFFSET values (but that's
> > > > again in sizetype,
On Thu, Aug 25, 2011 at 8:34 AM, Richard Guenther
wrote:
> On Thu, Aug 25, 2011 at 8:20 AM, Artem Shinkarov
> wrote:
>> Here is a cleaned-up patch without the hook. Mostly it works in a way
>> we discussed.
>>
>> So I think it is a right time to do something about vcond patterns,
>> which would a
On Fri, Aug 19, 2011 at 6:28 PM, Tom de Vries wrote:
> On 07/17/2011 08:33 PM, Tom de Vries wrote:
>> Updated version.
>>
>> On 06/08/2011 11:45 AM, Tom de Vries wrote:
>>> On 06/08/2011 11:42 AM, Tom de Vries wrote:
>>>
I'll send the patch with the testcases in a separate email.
>>>
>>
>
> 2
On Thu, Aug 25, 2011 at 8:20 AM, Artem Shinkarov
wrote:
> Here is a cleaned-up patch without the hook. Mostly it works in a way
> we discussed.
>
> So I think it is a right time to do something about vcond patterns,
> which would allow me to get rid of conversions that I need to put all
> over the
On Wed, Aug 24, 2011 at 9:00 PM, Ian Lance Taylor wrote:
> Tom de Vries writes:
>
>> Do you have a moment to give a second look to a gimple CFG optimization? The
>> optimization removes duplicate basic blocks and reduces code size by 1-2%.
>>
>> The latest patch is posted at
>> http://gcc.gnu.or
100 matches
Mail list logo