David Edelsohn wrote:
I am pleased to announce that the GCC Steering Committee has
appointed Jan Hubicka and Uros Bizjak as co-maintainers of the i386 port.
Thank you!
Please find attached the patch that updates my MAINTAINERS entry.
2007-01-09 Uros Bizjak <[EMAIL PROTECTED]>
Hello all,
1. How do i get the stack alignment size of a particular target?
Does #define STACK_BOUNDARY 32 serve this purpose?
2. Is it possible to override the STACK Alignment in ld file using ALIGN()?
3. Difference between stack alignment and data alignment?
Regards,
Rohit
H. J. Lu writes:
> I am enclosing a patch to implement a new linker swicth,
> --dynamic-list-data. It is -Bsymbolic for function symbols only.
> I tried it with C, C++, Java and Fortran on Linux/ia32, Linux/x86-64
> and Linux/ia64. There are only a few regressions. The function calls
> within
On Tue, Jan 09, 2007 at 01:38:00PM +, Andrew Haley wrote:
> H. J. Lu writes:
> > I am enclosing a patch to implement a new linker swicth,
> > --dynamic-list-data. It is -Bsymbolic for function symbols only.
> > I tried it with C, C++, Java and Fortran on Linux/ia32, Linux/x86-64
> > and Lin
H. J. Lu writes:
> On Tue, Jan 09, 2007 at 01:38:00PM +, Andrew Haley wrote:
> > H. J. Lu writes:
> > > I am enclosing a patch to implement a new linker swicth,
> > > --dynamic-list-data. It is -Bsymbolic for function symbols only.
> > > I tried it with C, C++, Java and Fortran on Linux
On Tue, Jan 09, 2007 at 01:51:00PM +, Andrew Haley wrote:
> H. J. Lu writes:
> > On Tue, Jan 09, 2007 at 01:38:00PM +, Andrew Haley wrote:
> > > H. J. Lu writes:
> > > > I am enclosing a patch to implement a new linker swicth,
> > > > --dynamic-list-data. It is -Bsymbolic for function
"Rohit Arul Raj" <[EMAIL PROTECTED]> writes:
> 1. How do i get the stack alignment size of a particular target?
>Does #define STACK_BOUNDARY 32 serve this purpose?
STACK_BOUNDARY is used to express the alignment maintained by the
hardware. In practice this means that gcc can expect the stack
H. J. Lu writes:
> On Tue, Jan 09, 2007 at 01:51:00PM +, Andrew Haley wrote:
> > H. J. Lu writes:
> > > On Tue, Jan 09, 2007 at 01:38:00PM +, Andrew Haley wrote:
> > > > H. J. Lu writes:
> > > > > I am enclosing a patch to implement a new linker swicth,
> > > > > --dynamic-list-
On Tue, Jan 09, 2007 at 02:01:53PM +, Andrew Haley wrote:
> H. J. Lu writes:
> > On Tue, Jan 09, 2007 at 01:51:00PM +, Andrew Haley wrote:
> > > H. J. Lu writes:
> > > > On Tue, Jan 09, 2007 at 01:38:00PM +, Andrew Haley wrote:
> > > > > H. J. Lu writes:
> > > > > > I am enclos
On Mon, Jan 08, 2007 at 08:23:39PM -0800, H. J. Lu wrote:
> On Mon, Jan 08, 2007 at 08:09:59PM -0800, Andrew Pinski wrote:
> > On Mon, 2007-01-08 at 18:25 -0800, H. J. Lu wrote:
> > > I am enclosing a patch to implement a new linker swicth,
> > > --dynamic-list-data. It is -Bsymbolic for function s
I am testing this patch now. It should fix the regresions when
libstdc++ is built with
-Bsymbolic-functions --dynamic-list-cpp-new
What about just --dynamic-list-cpp that enables the new behavior and
implies --dynamic-list-cpp-typeinfo (I know that it is useless in this
particular case, sin
On Tue, Jan 09, 2007 at 04:42:41PM +0100, Paolo Bonzini wrote:
>
> >I am testing this patch now. It should fix the regresions when
> >libstdc++ is built with
> >
> >-Bsymbolic-functions --dynamic-list-cpp-new
I tested it on gcc 4.2 with C, C++, Java and Fortran on Linux/x86-64.
There is no regres
Hi Alex,
this is the error message I'm getting:
/tmp/ccvk5vjH.s:38: Error: operand must be absolute in
range 1..32, not 53
I run on a Linux machine with AMD CPU (x86_64).
Ah yes this problem. I have encountered it too. Presumably you are
using a 64-bit Linux ? If you build in a 32-bit e
On Tue, Jan 09, 2007 at 06:18:19AM -0800, H. J. Lu wrote:
> On Tue, Jan 09, 2007 at 02:01:53PM +, Andrew Haley wrote:
> > H. J. Lu writes:
> > > On Tue, Jan 09, 2007 at 01:51:00PM +, Andrew Haley wrote:
> > > > H. J. Lu writes:
> > > > > On Tue, Jan 09, 2007 at 01:38:00PM +, Andrew
With LTO, an object file may contain sections with IL, which
can be discarded when building DSO and executable. Currently we can't
mark such sections with gABI. With GNU linker, we can use a
linker script to discard such sections. But it will be more generic
to make a section to be discarded for DS
"H. J. Lu" <[EMAIL PROTECTED]> writes:
> With LTO, an object file may contain sections with IL, which
> can be discarded when building DSO and executable. Currently we can't
> mark such sections with gABI. With GNU linker, we can use a
> linker script to discard such sections. But it will be more
On 09 Jan 2007 10:09:35 -0800, Ian Lance Taylor <[EMAIL PROTECTED]> wrote:
"H. J. Lu" <[EMAIL PROTECTED]> writes:
> With LTO, an object file may contain sections with IL, which
> can be discarded when building DSO and executable. Currently we can't
> mark such sections with gABI. With GNU linker
On Tue, Jan 09, 2007 at 10:09:35AM -0800, Ian Lance Taylor wrote:
>
> That is not strictly required for LTO as I see it. With LTO, the lto
> program is going to read the .o files with the IL information. It
> will then generate a new .s file to pass to the assembler. The IL
> information will n
On Tue, Jan 09, 2007 at 09:42:40AM -0800, H. J. Lu wrote:
> On Tue, Jan 09, 2007 at 06:18:19AM -0800, H. J. Lu wrote:
> > On Tue, Jan 09, 2007 at 02:01:53PM +, Andrew Haley wrote:
> > > H. J. Lu writes:
> > > > On Tue, Jan 09, 2007 at 01:51:00PM +, Andrew Haley wrote:
> > > > > H. J. Lu w
Does gcc support "delete (nothrow)"? I ran into 2 problems:
1. I had to call destructor directly since
A *p = new (std::nothrow) A;
delete (std::nothrow) p;
won't cpmpile. I had to use
A *p = new (std::nothrow) A;
...
operator delete (bb, std::nothrow);
2.
A *bb = new (std::nothrow) A [10];
H. J. Lu wrote:
With LTO, an object file may contain sections with IL, which
can be discarded when building DSO and executable. Currently we can't
mark such sections with gABI. With GNU linker, we can use a
linker script to discard such sections. But it will be more generic
to make a section to b
Hi Rod,
It looks like SHF_EXCLUDE is exactly what I am looking for. How useful
is it in your experiences?
Thanks.
H.J.
[EMAIL PROTECTED]
>-Original Message-
>From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On
>Behalf Of Rod Evans
>Sent: Tuesday, January 09, 2007 2:15 PM
>To: [EMAIL PR
On Tue, Jan 09, 2007 at 01:55:44PM -0800, H. J. Lu wrote:
> Does gcc support "delete (nothrow)"? I ran into 2 problems:
>
> 1. I had to call destructor directly since
>
> A *p = new (std::nothrow) A;
> delete (std::nothrow) p;
>
> won't cpmpile. I had to use
>
> A *p = new (std::nothrow) A;
>
On Tue, Jan 09, 2007 at 07:52:42AM -0800, H. J. Lu wrote:
> >
> > What about just --dynamic-list-cpp that enables the new behavior and
> > implies --dynamic-list-cpp-typeinfo (I know that it is useless in this
> > particular case, since C++ typeinfo is data, but in general such an
> > option so
Lu, Hongjiu wrote:
It looks like SHF_EXCLUDE is exactly what I am looking for. How useful
is it in your experiences?
As far as I can tell, this was introduced with the SYSTEM V APPLICATION
BINARY INTERFACE for the PowerPC Processor Supplement back in
September 1995 :-)
Then the Fortran folks
Rod Evans wrote:
Lu, Hongjiu wrote:
It looks like SHF_EXCLUDE is exactly what I am looking for. How useful
is it in your experiences?
As far as I can tell, this was introduced with the SYSTEM V APPLICATION
BINARY INTERFACE for the PowerPC Processor Supplement back in
September 1995 :-)
Then
Chris Pickett <[EMAIL PROTECTED]> writes:
| Hi,
|
| For one reason or another, I have spent a fair amount of time reading
| and getting confused by the warnings documentation. This applies to
| the optimizations as well, but I thought I would start with the
| warnings. Today I sat down and creat
27 matches
Mail list logo
