Thank you very much. This was very informative.
Richard Sandiford writes:
> If we have an instruction:
>
> A: (set (reg Z) (plus (reg X) (const_int 0xdeadbeef)))
>
> we will need to use something like:
>
>(set (reg Y) (const_int 0xdead))
>(set (reg Y) (ior (reg Y) (cons
Joseph S. Myers wrote:
> On Fri, 3 Apr 2009, Dave Korn wrote:
>
>> Got it: the key is that the types we use in our stdint.h target files have
>> to match the exact wording used at the top of c_common_nodes_and_builtins:
>
> This requirement is documented in tm.texi (under SIZE_TYPE, to which th
On Tue, 2009-04-07 at 23:45 -0700, Michael Eager wrote:
> I'm running the gcc test suite on powerpc-unknown-eabisim
> on the trunk and I get results which are different from
> one run to the next. When I run the failing tests by
> hand, all pass. Mike Stein also has noted that some of
> the test
Michael Eager wrote:
> Does anyone have any suggestions on how to get one of
> these tests to fail consistently, or a different approach
> to finding the cause of the intermittent failures?
Perhaps hack the testsuite to run the tests under gdb, setting a breakpoint
on abort() that causes it to
Hi Tom,
> All of IRIX 6.x is not equal and stdint.h was not added until IRIX 6.5.
it occured to me after I sent my mail.
> Please consider extending the patch to wrap stdint.h for any IRIX < 6.5
> and not just IRIX 5.
I don't have access to IRIX 6.2 any longer, but I'm pretty sure stdint.h
was
Dave Korn wrote:
> Roberto Bagnara wrote:
>
>> We have uploaded the first PPL 0.10.1 release candidate to
>
>> Please report any problem you may encounter to ppl-devel
>
> Hi Roberto and team,
>
> I am sorry to report some problems encountered.
I am pleased to report some problems reso
Am Samstag, den 21.03.2009, 11:59 +0100 schrieb John Holdsworth:
> I was wondering if it would be a useful extension to Objective-C
> expand the [] operator
> to support array and hash references to NSArray and NSDictionary
> classes directly to
> greatly improve the readability of code:
I'm
Dave Korn wrote:
Michael Eager wrote:
Does anyone have any suggestions on how to get one of
these tests to fail consistently, or a different approach
to finding the cause of the intermittent failures?
Perhaps hack the testsuite to run the tests under gdb, setting a breakpoint
on abort() tha
Hi,
while looking into problems of current and pretty-ipa's inlining heuristics
implementation, I noticed that we have relatively important problems with EH
overhead that confuse inliner code size metrics.
Looking deeper into EH problems, I think main issues are:
- Inliner tends to produce expo
On Wed, 8 Apr 2009, Jan Hubicka wrote:
> Some remaining issues:
> - FILTER_EXPR/OBJ_REF_EXPR is currently handled in quite dangerous way.
> Original Rth's code made them quite 100% volatile. Now we can PRE them.
> The FILTER_EXPR/OBJ_REF_EXPR are really hard registers in RTL world that
On Wed, 8 Apr 2009, Richard Guenther wrote:
> On Wed, 8 Apr 2009, Jan Hubicka wrote:
> > - The nature of code duplication in between cleanup at end of block and
> > cleanup in EH actually brings a lot of tail merging possibilities.
> > I wonder if we can handle this somehow effectivly on
> On Wed, 8 Apr 2009, Richard Guenther wrote:
>
> > On Wed, 8 Apr 2009, Jan Hubicka wrote:
> > > - The nature of code duplication in between cleanup at end of block and
> > > cleanup in EH actually brings a lot of tail merging possibilities.
> > > I wonder if we can handle this somehow e
On Wed, 8 Apr 2009, Jan Hubicka wrote:
> > On Wed, 8 Apr 2009, Richard Guenther wrote:
> >
> > > On Wed, 8 Apr 2009, Jan Hubicka wrote:
> > > > - The nature of code duplication in between cleanup at end of block
> > > > and
> > > > cleanup in EH actually brings a lot of tail merging possib
> For instance
> for (i=0; i can be optimized out for signed counter relying that overflow can jump
> in between max...INT_MAX
>
> togehter with loops of style
> for (i=0; i in unsigned, and for MAX known and safely away from end of type we
> should prove finiteness in most common cases.
Pleas
> On Wed, 8 Apr 2009, Jan Hubicka wrote:
>
> > Some remaining issues:
> > - FILTER_EXPR/OBJ_REF_EXPR is currently handled in quite dangerous way.
> > Original Rth's code made them quite 100% volatile. Now we can PRE them.
> > The FILTER_EXPR/OBJ_REF_EXPR are really hard registers in RTL
Steven Bosscher wrote:
On Wed, Apr 8, 2009 at 5:19 AM, Vladimir Makarov wrote:
I've been working on register-pressure sensitive insn scheduling last two
months and I hope to submit this work for gcc4.5. I am implementing also a
mode in insn-scheduler to do only live range shrinkage.
Is all o
Vladimir Makarov wrote:
Steven Bosscher wrote:
On Wed, Apr 8, 2009 at 5:19 AM, Vladimir Makarov
wrote:
I've been working on register-pressure sensitive insn scheduling last
two
months and I hope to submit this work for gcc4.5. I am implementing
also a
mode in insn-scheduler to do only live
GNU,
Is there an end-of-support date for GCC version 4.3.0? I'm assisting a
customer here at NAWCWD China Lake, California, to register software in our
Navy database, DADMS. In order to use (or purchase) software, it must be
approved in DADMS. One of the things we must show is proof of vendor
s
Hi!
I have made some progress with your help. I have fixed the sed part:
(1) there were missing 's' in the scripts, first I did not noticed it,
then I did not know if I was supposed to povide it;
(2) I have replaced the [ \t]+ by [ \t][ \t]*
to get:
--- ../_gcc_clean/fixincludes/inclhack.def
This merge simplified some code in the streamer as we no longer
need to worry about memory tags. It also exposed a couple of
bugs in EH handling (we were assuming that shared EH regions
always occurred when the original region was before the aliases
in the EH table) and in statement streaming (we
On Wed, Apr 8, 2009 at 5:19 PM, Richard Guenther wrote:
>> - We ought to be able to prove finitarity of simple loops so we can
>> DCE more early and won't rely on full loop unrolling to get rid of
>> empty loops originally initializing dead arrays.
>
> I wonder if CD-DCE should not catch
On Wed, Apr 8, 2009 at 6:50 PM, Nordvall, Gary USNUNK NAVAIR 33, ,
LEGACY SERVER wrote:
> GNU,
>
> Is there an end-of-support date for GCC version 4.3.0? I'm assisting a
> customer here at NAWCWD China Lake, California, to register software in our
> Navy database, DADMS. In order to use (or pur
On Wed, 2009-04-08 at 19:40 +0200, Richard Guenther wrote:
> On Wed, Apr 8, 2009 at 6:50 PM, Nordvall, Gary USNUNK NAVAIR 33, ,
> LEGACY SERVER wrote:
> > GNU,
> >
> > Is there an end-of-support date for GCC version 4.3.0? I'm assisting a
> > customer here at NAWCWD China Lake, California, to re
Naive user question : is this going to improve the efficiency
of throwing exceptions, at least in the restricted cases of :
- the catch clause contains the throw (after inlining).
- interprocedural analysis can connect the throwing spot and
the corresponding catch clause.
?
See my old PR 6588.
Sylvain Pion a écrit :
Naive user question : is this going to improve the efficiency
of throwing exceptions, at least in the restricted cases of :
- the catch clause contains the throw (after inlining).
I meant the try block, sorry.
- interprocedural analysis can connect th
> Normally with Commercial (COTS) software, the manufacturer has an
> end-of-support or end-of-life date, but I'm not sure how this works
> for free or open source software.
Pretty much the same way except that the company providing support is not
the "manufacturer". For both proprietary (what yo
> Sylvain Pion a écrit :
> >Naive user question : is this going to improve the efficiency
> >of throwing exceptions, at least in the restricted cases of :
There is little improvement already via EH cleanup: at least
cleanups/catch regions that turns out to be empty are now eliminated and
does not
On Wed, Apr 08, 2009 at 09:50:33AM -0700, Nordvall, Gary USNUNK NAVAIR 33, ,
LEGACY SERVER wrote:
> Is there an end-of-support date for GCC version 4.3.0?
(In this answer I'm speaking for myself only, not for GNU or GCC).
In one sense it already ended; there were three minor bug-fix releases
a
HI,
I wanna say thanks to everyone that help me.
My problem was find the correct path and the command line
I will expose what I did to help someone that can have the same problem.
I copied the files in my local path
$ cp debug /usr/local/bin/
$ cp debugx /usr/local/bin/
after I just run the de
I was wondering if loops of form
for (i=0; ; i++)
a[i]
can be assumed finite because eventaully a[i] would get to unallocated
memory otherwise. This is however similar to inifinite recursion
Correct me if I'm wrong but this is definitely wrong...
Assuming a 64bit processor and i to
Jan Hubicka a écrit :
Sylvain Pion a écrit :
Naive user question : is this going to improve the efficiency
of throwing exceptions, at least in the restricted cases of :
There is little improvement already via EH cleanup: at least
cleanups/catch regions that turns out to be empty are now elimin
Adam Nemet writes:
> Richard Sandiford writes:
>> If we have an instruction:
>>
>> A: (set (reg Z) (plus (reg X) (const_int 0xdeadbeef)))
>>
>> we will need to use something like:
>>
>>(set (reg Y) (const_int 0xdead))
>>(set (reg Y) (ior (reg Y) (const_int 0xbeef)))
>>
I've long wondered how GCC deals with C99 strict aliasing rules when
compiling Objective-C code. There's no language spec for Objective-C,
other than the written prose description of the language that Apple
provides (which, until recently, has been virtually unmodified since
it's NeXT origins), so
> Jan Hubicka a écrit :
> >>Sylvain Pion a écrit :
> >>>Naive user question : is this going to improve the efficiency
> >>>of throwing exceptions, at least in the restricted cases of :
> >
> >There is little improvement already via EH cleanup: at least
> >cleanups/catch regions that turns out to be
On Tue, 2009-04-07 at 12:32 +0200, Paolo Bonzini wrote:
> Thanks, this leaves out:
>
> r145593: http://gcc.gnu.org/ml/gcc-patches/2009-03/msg00545.html (i386)
> r145594: http://gcc.gnu.org/ml/gcc-patches/2009-03/msg00545.html (s390)
> r145597, r145598, r145599:
> http://gcc.gnu.org/ml/gcc-patches/
John Engelhart writes:
> Objective-C defines 'c_common_get_alias_set' as its language specific
> alias set manager. c_common_get_alias_set() seems(?) to only
> implement C's strict aliasing rules, with no provisions for
> Objective-C's needs.
> Can anyone with a much better understanding of GCC
On Tue, Apr 7, 2009 at 11:03 AM, Ramana Radhakrishnan
wrote:
>> To aid testing, I'd like people to help bootstrapping bootstrappable
>> targets -- arm, alpha, ia64, pa, s390, x86_64.
>
> I'm bootstrapping the branch on an arm-linux-gnueabi target.
bootstrap on arm-linux-gnueabi completed. Regress
Jan Hubicka a écrit :
EH throwing is so costly (2 cycles minimum reported in PR 6588) that,
in some cases, even if it's exceptional, like a 10^-4 probability
of throwing, you will see it show up on the profile.
Having EH delivery at reasonnable speed would really open up the design
space : i
Unfortunately this hasn't been tested for awhile, but it appears
that the x86_64-apple-darwin target no longer can build java. I am
seeing...
checking build system type... x86_64-apple-darwin10
checking host system type... x86_64-apple-darwin10
checking target system type... x86_64-apple-darwi
I see one place where breakage may have occured...
http://gcc.gnu.org/viewcvs/branches/gcc-4_4-branch/configure.ac?r1=144881&r2=144887
--- trunk/configure.ac 2009/03/16 13:23:13 144881
+++ trunk/configure.ac 2009/03/16 17:02:02 144887
@@ -446,11 +446,11 @@
*-*-chorusos)
nocon
>> r145655: http://gcc.gnu.org/ml/gcc-patches/2009-04/msg00492.html (testsuite)
>
> What's the point of the compile-only tests? It would be much more
> useful to have tests that execute and check that the results are
> correct for a variety of input values.
That's true. I went for compile-only
41 matches
Mail list logo
