Joern RENNECKE wrote:
In http://gcc.gnu.org/ml/gcc/2006-06/msg00120.html, you wrote:
As fwprop is no longer on the table for 4.2, and as the vectorizer
improvements seem to have stalled due to a combination of lack of review
and Dorit's leave, I think it's time to declare 4.2 feature-complete.
> This status report has been a long time coming, for which I apologize.
>
> As fwprop is no longer on the table for 4.2, and as the vectorizer
> improvements seem to have stalled due to a combination of lack of review
> and Dorit's leave,
That is unfortunate. Dorit did make a sincere effort to p
Wolfgang Mües <[EMAIL PROTECTED]> writes:
> On Sunday 04 June 2006 23:36, Rask Ingemann Lambertsen wrote:
>> On Wed, May 31, 2006 at 10:49:35PM +0200, Wolfgang Mües wrote:
>> > > (define_insn "*arm_movqi_insn"
>> > > [(set (match_operand:QI 0 "nonimmediate_operand" "=r,r,r,m")
>> > > (match_oper
ingw32
Configured with: ../gcc/configure --prefix=/tmp/mgw/mymingw --host=i686-pc-mingw
32 --target=i686-pc-mingw32 --disable-nls --disable-checking --disable-debug --e
nable-threads=win32 --disable-win32-registry --enable-languages=c --disable-werr
or
Thread model: win32
gcc version 4.2.0 20060606 (exp
On 6/6/06, Ayal Zaks <[EMAIL PROTECTED]> wrote:
> This status report has been a long time coming, for which I apologize.
>
> As fwprop is no longer on the table for 4.2, and as the vectorizer
> improvements seem to have stalled due to a combination of lack of review
> and Dorit's leave,
That is
Fengwei Yin wrote:
Hi Daniel,
I have already reported this bug. The bug number is #27363.
I also tried the gcc snapshot 4.1.1-20060421. The bug is not
fixed in this version too.
>
On 5/1/06, Daniel Jacobowitz <[EMAIL PROTECTED]> wrote:
On Sun, Apr 30, 2006 at 11:03:05AM +0800, Fengwei Yin wrot
On Tue, 2006-06-06 at 15:05, Dirk Behme wrote:
> Fengwei Yin wrote:
> > Hi Daniel,
> > I have already reported this bug. The bug number is #27363.
> > I also tried the gcc snapshot 4.1.1-20060421. The bug is not
> > fixed in this version too.
> >
> > On 5/1/06, Daniel Jacobowitz <[EMAIL PROTECTED]
On 06 June 2006 15:17, Richard Earnshaw wrote:
> On Tue, 2006-06-06 at 15:05, Dirk Behme wrote:
>> Fengwei Yin wrote:
>>> Hi Daniel,
>>> I have already reported this bug. The bug number is #27363.
>>> I also tried the gcc snapshot 4.1.1-20060421. The bug is not
>>> fixed in this version too.
>> >
Hi,
I'm updating a port from 3.4.6 to 4.1.1. In 3.4.6, I hadn't implemented
movmemsi patterns, but the compiler could still inline memcpy's (and also
strcpys where source string is a const) by itself. After updating to 4.1.1,
calls to memcpy are always generated.
I've had a bash at implementing
Hi,
i just built GCC 4.1.1 on AIX 5.1 using the following commands:
../gcc-4.1.1/configure --with-libiconv-prefix=/usr --disable-nls
--disable-multilib
make bootstrap-lean
make install
$ config.guess
powerpc-ibm-aix5.1.0.0
$ gcc -v
Using built-in specs.
Target: powerpc
You make a good point about the linker aspect but I was first most
concerned about the code generation differences, if any.
However, you are absolutely correct! A test is in order. I whipped up
a quick test program and was able to successfully compile, link and run
it, so it does indeed work!
On 06 June 2006 15:33, Dave Korn wrote:
> In the bug report, you wrote
"You" being Fengwei Yin, of course, not Dirk Behme; apologies for my unclear
attribution.
cheers,
DaveK
--
Can't think of a witty .sigline today
oops! forgot to cc the list. thanks Per.
- Forwarded Message
From: Per Bothner <[EMAIL PROTECTED]>
To: Davanum Srinivas <[EMAIL PROTECTED]>
Sent: Tuesday, June 6, 2006 11:49:23 AM
Subject: Re: GCC SC request about ecj
Davanum Srinivas wrote:
> Please see http://www.eclipsezone.com/eclips
Shantonu,
Thanks for the reply. I already figured out last night that
I could use the odcctools cvs to generate a new odcctools tarball
based on cctools-590.42.1. I was able to create an updated fink
odcctools package using that tarball.
I am bothering with this issue because I have noticed
In http://gcc.gnu.org/ml/gcc/2006-06/msg00185.html, your wrote:
So, two questions: any idea why 4.1.1 is no longer able to automatically
inline memcpys and why is the source operand for movmemsi not know to be as
widely aligned as it actually is?
See PR middle-end/27226
On Tue, Jun 06, 2006 at 08:16:54AM +0200, FX Coudert wrote:
>
> >>Something is marking random_seed as noreturn.
> >
> >As far as I understand, symbols are marked as noreturn by use of
> >TREE_THIS_VOLATILE, which is done on a few selected trees and is
> >also done whenever a symbol has the nor
> "Devang" == Devang Patel <[EMAIL PROTECTED]> writes:
Devang> This version removes internal radar numbers and replaces s/
Devang> DW_AT_APPLE.../DW_AT_GNU...
I read this. I'm not anywhere near an expert in dwarf or anything
related to this proposal, so please bear with me if I say something
On Tue, Jun 06, 2006 at 10:39:46AM +0100, Richard Sandiford wrote:
> Wolfgang Mües <[EMAIL PROTECTED]> writes:
> >> ../../../gcc-4.0.2/gcc/unwind-dw2-fde.c: In function
> >> __register_frame_info_table_bases':
> >> ../../../gcc-4.0.2/gcc/unwind-dw2-fde.c:146: error: insn does not
> >> satisfy its
Tom Tromey wrote:
"Devang" == Devang Patel <[EMAIL PROTECTED]> writes:
Devang> This version removes internal radar numbers and replaces s/
Devang> DW_AT_APPLE.../DW_AT_GNU...
I read this. I'm not anywhere near an expert in dwarf or anything
related to this proposal, so please bea
Tom Tromey wrote:
* Why put the optimization diary into the object file?
Why not just have -Wdiary and print it along with all the warnings?
(I'm sure there's an answer to this, it would just be nice if it
were in the document...)
These are not warnings and they should not cause build f
> These are not warnings and they should not cause build failures
> when -Werror is used, hence warnings are not suitable medium to
> communicate this info.
There is a third type of diagnostic in GCC which gets not much
use at all. It is called note. It might be interesting to use that instead
o
Andrew Pinski wrote:
These are not warnings and they should not cause build failures
when -Werror is used, hence warnings are not suitable medium to
communicate this info.
There is a third type of diagnostic in GCC which gets not much
use at all. It is called note. It might be interestin
>
> Andrew Pinski wrote:
> >> These are not warnings and they should not cause build failures
> >> when -Werror is used, hence warnings are not suitable medium to
> >> communicate this info.
> >>
> >
> > There is a third type of diagnostic in GCC which gets not much
> > use at all. It is cal
On Tue, Jun 06, 2006 at 07:42:20AM +0200, Wolfgang Mües wrote:
> Rask,
>
> On Monday 05 June 2006 16:16, Rask Ingemann Lambertsen wrote:
> > I think the comment in arm.h is wrong. The manual seems to agree with
> > the code.
>
> Just to make it easy for beginners...
In mainline GCC, it is defin
I've studied a fair bit of analytic philosophy and feel that it is
the rigorous arguments and detailed justification that separates
worthwhile philosophy from mere speculation or faith based spiritual
musings. Is there any reason for someone like me to take Hegel
seriously? You've talke
Ignore that last email. It was sent to the wrong address.
Peter
Peter Gerdes -- [EMAIL PROTECTED]
Find what I have to say interesting? Check out my blog or my
analytic philosophy blog.
On Jun 6, 2006, at 12:36 PM, Peter Michael Gerdes wrote:
I've studied a fair bit of analytic phi
On 6/6/06, Peter Michael Gerdes <[EMAIL PROTECTED]> wrote:
Ignore that last email. It was sent to the wrong address.
Thesis, antithesis, synthesis.
--
David L Nicol
"fans of liza minelli should always be
disconnected immediately" -- Matthew Henry
Andrew Pinski wrote:
Andrew Pinski wrote:
These are not warnings and they should not cause build failures
when -Werror is used, hence warnings are not suitable medium to
communicate this info.
There is a third type of diagnostic in GCC which gets not much
use at all. It is c
On Tue, Jun 06, 2006 at 12:36:42PM -0700, Peter Michael Gerdes wrote:
>
> Does Hegel actually have good arguments for his views or is he just
> musing and throwing out ideas? If not why should we take him seriously?
I don't think any of his patches have been accepted by GCC, so I'd say
his arg
Devang Patel <[EMAIL PROTECTED]> writes:
| Tom Tromey wrote:
| > * Why put the optimization diary into the object file?
| > Why not just have -Wdiary and print it along with all the warnings?
| > (I'm sure there's an answer to this, it would just be nice if it
| > were in the document...)
|
Devang Patel <[EMAIL PROTECTED]> writes:
| [ Interestingly, there is a long standing request, here at Apple, to list
| command line options in object file (even when optimization is not used).
| One of our intern tried to put them in STABS string. It may be a good
| idea to use DWARF in that
Hi Devang,
> -
> Devang
>
> [ Interestingly, there is a long standing request, here at Apple, to list
> command line options in object file (even when optimization is not used).
> One of our intern tried to put them in STABS string. It may be a good
> idea to use DWARF in that case also. H
On Tue, Jun 06, 2006 at 03:47:59PM -0500, Gabriel Dos Reis wrote:
> Devang Patel <[EMAIL PROTECTED]> writes:
>
> | [ Interestingly, there is a long standing request, here at Apple, to list
> | command line options in object file (even when optimization is not used).
> | One of our intern tried
Is this what you want ?
yes :)
Thanks,
-
Devang
On Mon, Jun 05, 2006 at 09:53:00PM -0700, Andrew Pinski wrote:
> Also what about moving the News up to a noticeable spot since right now
> it is down in a corner so it looks out of place. In fact on my screen
> which is set to 1024x768, I have to scroll to get to the news.
Yes, the top news needs
Tom Tromey wrote:
>> "Devang" == Devang Patel <[EMAIL PROTECTED]> writes:
>
> Devang> This version removes internal radar numbers and replaces s/
> Devang> DW_AT_APPLE.../DW_AT_GNU...
>
> I read this. I'm not anywhere near an expert in dwarf or anything
> related to this proposal, so please
On Tue, 6 Jun 2006, Daniel Jacobowitz wrote:
| On Tue, Jun 06, 2006 at 03:47:59PM -0500, Gabriel Dos Reis wrote:
| > Devang Patel <[EMAIL PROTECTED]> writes:
| >
| > | [ Interestingly, there is a long standing request, here at Apple, to list
| > | command line options in object file (even when o
> "Devang" == Devang Patel <[EMAIL PROTECTED]> writes:
Tom> * Why put the optimization diary into the object file?
[...]
Devang> 2) This info is consumed by other tools (e.g. IDE, performance
Devang> analyzer). It makes sense for a tool like Shark to use dwarf
Devang> reader to get this inf
> "Devang" == Devang Patel <[EMAIL PROTECTED]> writes:
>> * DW_AT_GNU_OD_cmd - it seems strange for this to be defined in terms
>> of text highlighting. Why have a separate code here for "dead
>> code" instead of just marking a text region and having a new _msg
>> value meaning "dead code"?
> "Dan" == Daniel Berlin <[EMAIL PROTECTED]> writes:
Dan> In addition to Tom's concerns, it seems to me to be a *really bad idea*
Dan> to try to come up with integer values for every single message, instead
Dan> of just placing a string there.
One reason to prefer the numerical approach is th
Daniel Berlin <[EMAIL PROTECTED]> writes:
> Tom Tromey wrote:
> >> "Devang" == Devang Patel <[EMAIL PROTECTED]> writes:
> >
> > Devang> This version removes internal radar numbers and replaces s/
> > Devang> DW_AT_APPLE.../DW_AT_GNU...
> >
> > I read this. I'm not anywhere near an expert in
Geoffrey Keating wrote:
> Daniel Berlin <[EMAIL PROTECTED]> writes:
>
>> Tom Tromey wrote:
"Devang" == Devang Patel <[EMAIL PROTECTED]> writes:
>>> Devang> This version removes internal radar numbers and replaces s/
>>> Devang> DW_AT_APPLE.../DW_AT_GNU...
>>>
>>> I read this. I'm not any
>
> Trying to catalogue and assign a permanent place and number to every
> single optimization message a compiler can generate is a much much much
> worse idea, IMHO.
In the same way numbering warning messages is a bad idea (yes ICC and a couple
other compilers do but we should not).
-- Pinski
On 06/06/2006, at 4:58 PM, Daniel Berlin wrote:
Geoffrey Keating wrote:
Daniel Berlin <[EMAIL PROTECTED]> writes:
Tom Tromey wrote:
"Devang" == Devang Patel <[EMAIL PROTECTED]> writes:
Devang> This version removes internal radar numbers and replaces s/
Devang> DW_AT_APPLE.../DW_AT_GNU...
Geoffrey Keating wrote:
> On 06/06/2006, at 4:58 PM, Daniel Berlin wrote:
>
>> Geoffrey Keating wrote:
>>> Daniel Berlin <[EMAIL PROTECTED]> writes:
>>>
Tom Tromey wrote:
>> "Devang" == Devang Patel <[EMAIL PROTECTED]> writes:
> Devang> This version removes internal radar numbers
On 06/06/2006, at 5:11 PM, Daniel Berlin wrote:
Geoffrey Keating wrote:
On 06/06/2006, at 4:58 PM, Daniel Berlin wrote:
Geoffrey Keating wrote:
Daniel Berlin <[EMAIL PROTECTED]> writes:
Tom Tromey wrote:
"Devang" == Devang Patel <[EMAIL PROTECTED]> writes:
Devang> This version removes in
> Right above, you said "We control the debug output machinery
> generating this, and can simply tell it to only deal in one
> language." Here, you seem to be implying that the messages should be
> localised in the language the compiler is going to output messages
> in. I suppose you coul
On 06/06/2006, at 5:20 PM, Andrew Pinski wrote:
Right above, you said "We control the debug output machinery
generating this, and can simply tell it to only deal in one
language." Here, you seem to be implying that the messages should be
localised in the language the compiler is going to outpu
>
>
> --Apple-Mail-9--465959030
> Content-Transfer-Encoding: 7bit
> Content-Type: text/plain;
> charset=US-ASCII;
> delsp=yes;
> format=flowed
>
>
> On 06/06/2006, at 5:20 PM, Andrew Pinski wrote:
>
> >> Right above, you said "We control the debug output machinery
> >> genera
On 06/06/2006, at 5:25 PM, Andrew Pinski wrote:
On 06/06/2006, at 5:20 PM, Andrew Pinski wrote:
Right above, you said "We control the debug output machinery
generating this, and can simply tell it to only deal in one
language." Here, you seem to be implying that the messages
should be
loc
> I don't see how making it a string makes this different. Either your
> new string will be a standard string or it won't. Either your new
> number will be a standard number or it won't. If you want it to be
> standard, you have to go through the committee.
I don't understand why it has t
I believe I may have discovered the component that was causing the
c++ regressions I was seeing on Darwin when fink was sourced. I have
found that after I deinstalled bison v2.1 installed by fink, I was
able to build gcc trunk on MacOS X 10.4 with fink sourced and still
pass the c++ testsuite pr
On Tue, Jun 06, 2006 at 05:36:33PM -0700, Geoffrey Keating wrote:
> I don't see how making it a string makes this different. Either your
> new string will be a standard string or it won't. Either your new
> number will be a standard number or it won't. If you want it to be
> standard, you
Hi, all,
After I refer to the Intel paper titled "Threading
Methodology : Principles and Practices" versin 2.0
published in 2003, I note the following message in the
article mentioning:(from page 22, web site :
http://cache-www.intel.com/cd/00/00/21/93/219349_threadingmethodology.pdf)
___
Daniel Jacobowitz wrote:
On Tue, Jun 06, 2006 at 05:36:33PM -0700, Geoffrey Keating wrote:
I don't see how making it a string makes this different. Either your
new string will be a standard string or it won't. Either your new
number will be a standard number or it won't. If you want it
Tom Tromey wrote:
"Devang" == Devang Patel <[EMAIL PROTECTED]> writes:
Tom> * Why put the optimization diary into the object file?
[...]
Devang> 2) This info is consumed by other tools (e.g. IDE, performance
Devang> analyzer). It makes sense for a tool like Shark to use dwarf
De
On Jun 6, 2006, at 9:49 PM, Devang Patel wrote:
We can allocate space in numbering for vendor extensions.
What happens when you compile two sources with two different
compilers and they
use the same number for vendor extension? You just end up with weird
results
in the IDE or performance
Tom Tromey wrote:
"Devang" == Devang Patel <[EMAIL PROTECTED]> writes:
* DW_AT_GNU_OD_cmd - it seems strange for this to be defined in terms
of text highlighting. Why have a separate code here for "dead
code" instead of just marking a text region and having a new _msg
value me
Rask,
On Tuesday 06 June 2006 21:33, Rask Ingemann Lambertsen wrote:
> > > + swp%?b\\t%1, %1, %0\;ldr%?b\\t%1, %0"
> >
> > You should get a price for cleverness here!
>
> Thanks! Indeed it looks good until you think of volatile variables.
Because volatile variables can change their values from
Andrew Pinski wrote:
On Jun 6, 2006, at 9:49 PM, Devang Patel wrote:
We can allocate space in numbering for vendor extensions.
What happens when you compile two sources with two different compilers
and they
use the same number for vendor extension?
What happens when another compiler uses
On Jun 6, 2006, at 10:34 PM, Devang Patel wrote:
Andrew Pinski wrote:
On Jun 6, 2006, at 9:49 PM, Devang Patel wrote:
We can allocate space in numbering for vendor extensions.
What happens when you compile two sources with two different
compilers and they
use the same number for vendor
I have finished a build of gcc trunk on Darwin with a fink package
of bison 2.3 installed and can confirm that the c++ regressions I saw
with bison 2.1 installed have disappeared. So there must be some problem
with bison 2.1 and gcc trunk (at least on Darwin).
Jack
62 matches
Mail list logo
