Daniel Berlin wrote:
>> PR 32328 -fstrict-aliasing ...
>
> This i have a patch for, but it really needs some performance testing.
> I'm happy to throw it in RC2 if you want to see how it does, with the
> caveat it may need to be pulled back out if it causes massive
> performance regressions :)
N
Revital1 Eres <[EMAIL PROTECTED]> writes:
> The following ICE is received on r126521 while bootstraping on ppc64.
This should be fixed by revision 126536. Sorry for the problems.
Ian
Sandra Loosemore <[EMAIL PROTECTED]> writes:
> The error reported here
>
> http://gcc.gnu.org/ml/gcc/2007-07/msg00339.html
>
> is also happening when building for target mipsisa32r2-elfoabi on
> i686-pc-linux-gnu.
This should be fixed by revision 126536. Sorry for the problems.
Ian
On 7/11/07, Mark Mitchell <[EMAIL PROTECTED]> wrote:
Summary
---
The next scheduled GCC 4.2.x release is GCC 4.2.1 on July 13th.
As of 5PM PDT tomorrow, please consider the 4.2 branch closed to all
changes. If you have outstanding changes that have been approved, but
not committed, make t
Summary
---
The next scheduled GCC 4.2.x release is GCC 4.2.1 on July 13th.
As of 5PM PDT tomorrow, please consider the 4.2 branch closed to all
changes. If you have outstanding changes that have been approved, but
not committed, make the commits before that time. I plan to build GCC
4.2.1
The error reported here
http://gcc.gnu.org/ml/gcc/2007-07/msg00339.html
is also happening when building for target mipsisa32r2-elfoabi on
i686-pc-linux-gnu.
-Sandra
> >
> > I am on that tricky thing ;) I think I need in i386.c an global variable
> > "ix86_amd64_abi" which helds the the current function abi. This means also
> > that I have to use instead of TARGET_64BIT_MS_ABI this variable. This var
> > may initioalized by init_cumulative_args and the over
One of the best things about the GCC Summit is the opportunity to
meet other developers and users of GCC and chat with them informally
during breaks, meals, pub night, and the final party. This year the
GCC Summit will provide new opportunities to share information with
other summit participants:
Janis Johnson <[EMAIL PROTECTED]> writes:
> There's a testsuite patch that I submitted, but haven't yet
> checked in, that will break test summary comparisons from before
> and after that patch is applied:
>
> http://gcc.gnu.org/ml/gcc-patches/2007-06/msg00834.html
> http://gcc.gnu.org/ml/gcc-pat
On 7/10/07, [EMAIL PROTECTED] <[EMAIL PROTECTED]> wrote:
>In a message dated 7/9/2007 2:37:03 P.M. Pacific Daylight Time,
[EMAIL PROTECTED] writes:
>On 7/9/07, [EMAIL PROTECTED] <[EMAIL PROTECTED]> wrote:
>> >In a message dated 7/7/2007 4:04:01 A.M. Pacific Daylight Time, Rob1weld
>> writes:
On 7/10/07, Nicolas Alt <[EMAIL PROTECTED]> wrote:
Ok - so question is if x86_64 is completely implemented already. For
our case, especially the MS ABI. Andrew, do you have any knowledge if
they introduced a new calling convention and how they named it?
It is only implemented for the x86_64-min
Ok - so question is if x86_64 is completely implemented already. For
our case, especially the MS ABI. Andrew, do you have any knowledge if
they introduced a new calling convention and how they named it?
Nicolas
On Jul 10, 2007, at 13:29 , Andrew Pinski wrote:
On 7/10/07, Nicolas Alt <[EMA
On 7/10/07, Nicolas Alt <[EMAIL PROTECTED]> wrote:
That's cool! What version would you do the patch for?
Apart from wine, I guess mingw should have the biggest need for the
MS ABI in order to support AMD64.
mingw x86_64 support is already added for 4.3 on the trunk.
Thanks,
Andrew Pinski
That's cool! What version would you do the patch for?
Apart from wine, I guess mingw should have the biggest need for the
MS ABI in order to support AMD64.
Nicolas
On Jul 10, 2007, at 5:59 , Kai Tietz wrote:
Windows and GCC ABIs are on x86-64 more different than that (they
was
historicall
Hello,
The following ICE is received on r126521 while bootstraping on ppc64.
Revital
/home/eres/test_again/build/./gcc/xgcc -B/home/eres/test_again/build/./gcc/
-B/home/eres/test_again/build/powerpc64-unknown-linux-gnu/bin/
-B/home/eres/test_again/build/powerpc64-unknown-linux-gnu/lib/ -isystem
There's a testsuite patch that I submitted, but haven't yet
checked in, that will break test summary comparisons from before
and after that patch is applied:
http://gcc.gnu.org/ml/gcc-patches/2007-06/msg00834.html
http://gcc.gnu.org/ml/gcc-patches/2007-06/msg01076.html
A patch from Manuel López-I
Michael Veksler wrote:
> >What do you think?
On Tue, Jul 10, 2007 at 06:58:50PM +0200, Paolo Carlini wrote:
> I think that the "current" solution is very, very old, and "heaven"
> knows how many others didn't work at the time on some "exotic"
> platforms. I would suggest filing a PR and CCing B
On 10 Jul 2007 09:51:14 -0700, Ian Lance Taylor <[EMAIL PROTECTED]> wrote:
"Sunzir Deepur" <[EMAIL PROTECTED]> writes:
> What files are the sources of crtbegin.o and crtend.o ?
The single file gcc/crtstuff.c.
> What's their purposes ?
To ensure that global constructors and destructors are run
Michael Veksler wrote:
What do you think?
I think that the "current" solution is very, very old, and "heaven"
knows how many others didn't work at the time on some "exotic"
platforms. I would suggest filing a PR and CCing Benjamin.
Thanks,
Paolo.
"Sunzir Deepur" <[EMAIL PROTECTED]> writes:
> What files are the sources of crtbegin.o and crtend.o ?
The single file gcc/crtstuff.c.
> What's their purposes ?
To ensure that global constructors and destructors are run at the
appropriate times (i.e., before main and after exit, respectively).
Hello,
Currently libstdc++ violates ODR:
iostream: extern ostream cout;
global_io.cc: fake_ostream cout;
It assumes that gcc will work fine with this. Apparently it does, for now.
After solving a similar problem in my code using a similar technique -
to find out that it does not work for M
Hi Richard,
On 7/10/07, Richard Guenther <[EMAIL PROTECTED]> wrote:
On 7/10/07, Ramana Radhakrishnan <[EMAIL PROTECTED]> wrote:
> Hi,
>
> While upgrading a port of mine to trunk for a testcase I noticed the
> following . Its more of a question for a language lawyer I guess.
>
> The test looks
PS: since apparently people would like that, I decided to implement
immediately 20.2.2 of the working draft, thus std::identity,
std::forward and std::move. Will be available in in one of the
next snapshots of 4.3...
Thanks,
Paolo.
On 7/10/07, Ramana Radhakrishnan <[EMAIL PROTECTED]> wrote:
Hi,
While upgrading a port of mine to trunk for a testcase I noticed the
following . Its more of a question for a language lawyer I guess.
The test looks like this.
int spinlock[2];
void foo (void)
{
volatile int * spinlock0;
while
Hi,
While upgrading a port of mine to trunk for a testcase I noticed the
following . Its more of a question for a language lawyer I guess.
The test looks like this.
int spinlock[2];
void foo (void)
{
volatile int * spinlock0;
while (*spinlock0 == 0)
{
/* do nothing */
}
}
Store CCP folds awa
>
> I am on that tricky thing ;) I think I need in i386.c an global variable
> "ix86_amd64_abi" which helds the the current function abi. This means also
> that I have to use instead of TARGET_64BIT_MS_ABI this variable. This var
> may initioalized by init_cumulative_args and the overriden
> R
fafa wrote:
Hi all,
I tried to compile some rvalue reference examples by (from H.Hinnant at
http://home.twcny.rr.com/hinnant/cpp_extensions/rvalue_ref_rationale.html)
with one of the latest GCC 4.3 snapshots, but I'm getting
error: 'move' is not a member of 'std'
What can I do to get th
Hi all,
I tried to compile some rvalue reference examples by (from H.Hinnant at
http://home.twcny.rr.com/hinnant/cpp_extensions/rvalue_ref_rationale.html)
with one of the latest GCC 4.3 snapshots, but I'm getting
error: 'move' is not a member of 'std'
What can I do to get this working ?
Hi all,
What files are the sources of crtbegin.o and crtend.o ?
What's their purposes ?
thank you
sunzir
> > >
> > > For MS I would probably suggest ms_abi (it makes it cleaner that the
> > > attribute is affecting calling convetion). For our abi I am not
sure, we
> > > can sysv_abi or something else...
> >
> > I will prepare an patch for it. For me "ms_abi" and "sysv_abi" is
fine.
>
> I would sa
Richard Kenner wrote:
Will gcc add the optimization support in the future (method 1)?
Since GCC is a volunteer project, the answer for any sort of question
like that is "if somebody writes it, it'll exist and if they don't, it
won't". There's no good way to predict what projects people will fi
> >
> > For MS I would probably suggest ms_abi (it makes it cleaner that the
> > attribute is affecting calling convetion). For our abi I am not sure, we
> > can sysv_abi or something else...
>
> I will prepare an patch for it. For me "ms_abi" and "sysv_abi" is fine.
I would say that it is in ge
[EMAIL PROTECTED] writes:
> Please look at this page:
> _http://www.cs.nyu.edu/leunga/www/MLRISC/Doc/html/mlrisc-ir.html_
> (http://www.cs.nyu.edu/leunga/www/MLRISC/Doc/html/mlrisc-ir.html)
That tells me about the MLRISC IR, but it doesn't tell me what
significant advantages it has over GIMPLE.
> > > Windows and GCC ABIs are on x86-64 more different than that (they
was
> > > historically developed in parallel). GCC 4.3 will support attribute
for
> > > this calling convention contributed by Kai Tiez and Richard
Henderson,
> > > but before that there is not much to do...
> > Note: My nam
> > Windows and GCC ABIs are on x86-64 more different than that (they was
> > historically developed in parallel). GCC 4.3 will support attribute for
> > this calling convention contributed by Kai Tiez and Richard Henderson,
> > but before that there is not much to do...
> Note: My name is Kai Tiet
> > On 09 July 2007 20:48, Nicolas Alt wrote:
> >
> > > Hi!
> > >
> > > On the AMD64 / x86-64Bit architecture, some arguments of a functions
> > > are passed using registers, but there seem to be two different
> > > conventions out there. The standard ABI uses 6 registers, but
> > > Microsoft com
> On 09 July 2007 20:48, Nicolas Alt wrote:
>
> > Hi!
> >
> > On the AMD64 / x86-64Bit architecture, some arguments of a functions
> > are passed using registers, but there seem to be two different
> > conventions out there. The standard ABI uses 6 registers, but
> > Microsoft compilers use only
Hi Dave,
> Better show us your configure line then. What host type is this cross
for?
I used for configure just "--target=x86_64-pc-mingw32".
Cheers,
i.A. Kai Tietz
| (\_/) This is Bunny. Copy and paste Bunny
| (='.'=) into your signature to help him gain
| (")_(") world domination.
> Will gcc add the optimization support in the future (method 1)?
Since GCC is a volunteer project, the answer for any sort of question
like that is "if somebody writes it, it'll exist and if they don't, it
won't". There's no good way to predict what projects people will find
interesting.
Hi Danny,
> How else can you initialize and clean up the Dwarf2 unwind
> registrations on x86_64-pc-mingw32?
Clear ;) But I meant, why those objects are not build for this target in
(lib)gcc ?
Cheers,
i.A. Kai Tietz
| (\_/) This is Bunny. Copy and paste Bunny
| (='.'=) into your signature
On 10 July 2007 12:38, Kai Tietz wrote:
> "Dave Korn" wrote on 10.07.2007 13:24:30:
>
>> On 10 July 2007 12:19, Kai Tietz wrote:
>>
>> Are you trying to rebuild in an old objdir from before the patch?
>> I found that something didn't work as I had hoped in the
>> dependencies and I had to blow
"Dave Korn" wrote on 10.07.2007 13:24:30:
> On 10 July 2007 12:19, Kai Tietz wrote:
>
> Are you trying to rebuild in an old objdir from before the patch?
> I found that something didn't work as I had hoped in the
> dependencies and I had to blow away my existing build dir and
> configure fro
Kai Tietz
Tuesday, 10 July 2007 11:19 p.m.
>
> Hi,
>
> I tried to build the cross-compiler for the target
> x86_64-pc-mingw32 and
> noticed some trouble about the crtbegin and crtend for this
> target. To the
> specfile this object was introduced by the patch of Danny
> Smith from the
> 14
On 10 July 2007 12:19, Kai Tietz wrote:
> Hi,
>
> I tried to build the cross-compiler for the target x86_64-pc-mingw32 and
> noticed some trouble about the crtbegin and crtend for this target. To the
> specfile this object was introduced by the patch of Danny Smith from the
> 14th of Jine 2007. T
Hi,
I tried to build the cross-compiler for the target x86_64-pc-mingw32 and
noticed some trouble about the crtbegin and crtend for this target. To the
specfile this object was introduced by the patch of Danny Smith from the
14th of Jine 2007. The problem is, that those objects are not compiled
>In a message dated 7/9/2007 2:37:03 P.M. Pacific Daylight Time,
[EMAIL PROTECTED] writes:
>On 7/9/07, [EMAIL PROTECTED] <[EMAIL PROTECTED]> wrote:
>> >In a message dated 7/7/2007 4:04:01 A.M. Pacific Daylight Time, Rob1weld
>> writes:
>> >This page http://deputy.cs.berkeley.edu/ has a link
Hi Jim,
Thanks very much for your email. Will gcc add the optimization support
in the future (method 1)? For method 2, if abs accept short/char, may
I give the function names as sabs and qabs? Gcc does already have cabs
as complex abs, doesn't it?
Best regards
Maggie
Quoting Jim Wilson
47 matches
Mail list logo
