On Wed, Oct 29, 2008 at 6:19 AM, S. Suhasini
<[EMAIL PROTECTED]> wrote:
> We would like to know whether the new version of the software (compiled with
> the new GCC) can be deployed and run on the older setup with RHEL AS 3 and
> GCC 2.96. We need not compile again on the older setup. Will there be
On Tue, Oct 28, 2008 at 8:02 PM, Manuel López-Ibáñez
<[EMAIL PROTECTED]> wrote:
> 2008/10/25 Daniel Berlin <[EMAIL PROTECTED]>:
>> I have placed a continuous builder (IE it does one build per svn
>> change) for GCC for x86_64 on an 8 core machine (nicely provided by
>> Google), and it has results
How are you today?
I write to inform you that we have already sent you USD6000.00 dollars through
Western union as we have been given the mandate to transfer your full
compensation payment total sum of USD800,000.00 via western union by this
governemnt.I was calling your telephone number to g
2008/10/29 Daniel Berlin <[EMAIL PROTECTED]>:
> The patch tracker was an experiment in trying to see if it would
> improve the rate of patches falling through the cracks.
> It had the secondary effect of getting some other patches reviewed
> quicker in some cases, because of those who paid attentio
Steven Bosscher wrote:
On Wed, Oct 29, 2008 at 6:19 AM, S. Suhasini
<[EMAIL PROTECTED]> wrote:
We would like to know whether the new version of the software (compiled with
the new GCC) can be deployed and run on the older setup with RHEL AS 3 and
GCC 2.96. We need not compile again on the old
On Wed, Oct 29, 2008 at 9:16 AM, Manuel López-Ibáñez
<[EMAIL PROTECTED]> wrote:
> 2008/10/29 Daniel Berlin <[EMAIL PROTECTED]>:
>> The patch tracker was an experiment in trying to see if it would
>> improve the rate of patches falling through the cracks.
>> It had the secondary effect of getting so
Hi,
Suppose I have a class B in namespace A, it has several overloaded
member function doit.
I'm wondering how to find all the lines where there is a statement
that calls one particular overloaded doit member function? Is it
possible to do so from g++ command line? Or I have to modify g++ to
make
"Daniel Berlin" <[EMAIL PROTECTED]> writes:
>> A bi-weekly status report of the patch tracker sent to gcc-patches
>> would definitively make the list of unreviewed patches more visible. I
>> believe this may also be a problem for the continuous builder: If
>> there is no visible feedback from it,
Hello Everyone,
I have a question regarding the register allocation steps in GCC. I
am creating an hypothetical example to make things easy.
My processor has 2 set of register fiels with 1-16 in Class1 and
16-32 in class 2
Let's say I have an RTL X with destination register R1, But
2008/10/29 Daniel Berlin <[EMAIL PROTECTED]>:
>>
>> I agree that the patch tracker probably does not get more patches
>> reviewed but it definitely gets less patches lost.
>
> But in the end, it didn't solve the underlying problem, so it didn't
> improve our rate of attrition of smaller contributor
Hi!
Nick/Vlad, could you please check your editors? Your
recent r141295 and r141383 commits mangled many UTF-8 characters
in gcc/ChangeLog.
I've reverted those parts of your commits as r141428, just wouldn't like to
do it too often.
Thanks.
Jakub
On Wed, Oct 29, 2008 at 11:42 AM, Ian Lance Taylor <[EMAIL PROTECTED]> wrote:
> "Daniel Berlin" <[EMAIL PROTECTED]> writes:
>
>>> A bi-weekly status report of the patch tracker sent to gcc-patches
>>> would definitively make the list of unreviewed patches more visible. I
>>> believe this may also b
Ian Lance Taylor wrote on 29 October 2008 15:42:
> "Daniel Berlin" <[EMAIL PROTECTED]> writes:
>
>>> A bi-weekly status report of the patch tracker sent to gcc-patches
>>> would definitively make the list of unreviewed patches more visible. I
>>> believe this may also be a problem for the continu
On Wed, Oct 29, 2008 at 8:42 AM, Ian Lance Taylor <[EMAIL PROTECTED]> wrote:
> "Daniel Berlin" <[EMAIL PROTECTED]> writes:
> Back at Cygnus I wrote a script which sent out a daily report for bugs
> which had not been fixed, and I think it was very helpful. A daily
> report is not appropriate here,
> Let's say I have an RTL X with destination register R1, But if I
> want to schedule this RTL to Class2. What can I do? I see that GCC
> doesn't change the register number if it already holds a hard-register.
Use constraints. They are described in md.texi.
Snapshot gcc-4.2-20081029 is now available on
ftp://gcc.gnu.org/pub/gcc/snapshots/4.2-20081029/
and on various mirrors, see http://gcc.gnu.org/mirrors.html for details.
This snapshot has been generated from the GCC 4.2 SVN branch
with the following options: svn://gcc.gnu.org/svn/gcc/branches
"Andrew Pinski" <[EMAIL PROTECTED]> writes:
> On Wed, Oct 29, 2008 at 8:42 AM, Ian Lance Taylor <[EMAIL PROTECTED]> wrote:
>> "Daniel Berlin" <[EMAIL PROTECTED]> writes:
>> Back at Cygnus I wrote a script which sent out a daily report for bugs
>> which had not been fixed, and I think it was very h
On Wed, Oct 29, 2008 at 3:48 PM, Ian Lance Taylor <[EMAIL PROTECTED]> wrote:
> It needs to be a summary report, not one message per patch. Does
> bugzilla have that capability?
Yes, here is an example of the whine report (from yesterday):
Click here to edit your whine schedule
Assigned bugs
ID
18 matches
Mail list logo