On Thu, Feb 16, 2006 at 03:28:46PM +, Paul Brook wrote:
> > The point is that from a gfortran perspective -mlong-double-128 doesn't
> > change the ABI, it merely adds to it (which is sort of a change, but less
> > invasive than changing long double from 8bytes to 16bytes). So we can
> > easily
On Thursday 16 February 2006 15:18, Richard Guenther wrote:
> On 2/16/06, Paul Brook <[EMAIL PROTECTED]> wrote:
> > On Thursday 16 February 2006 11:09, François-Xavier Coudert wrote:
> > > Hi all,
> > >
> > > I'm sending this mail because I'm a bit confused about the
> > > -mlong-double-128 option
>
> On 2/16/06, Paul Brook <[EMAIL PROTECTED]> wrote:
> > On Thursday 16 February 2006 11:09, François-Xavier Coudert wrote:
> > > Hi all,
> > >
> > > I'm sending this mail because I'm a bit confused about the
> > > -mlong-double-128 option on (for example) ppc64-linux, and its impact
> > > on gfo
On 2/16/06, Paul Brook <[EMAIL PROTECTED]> wrote:
> On Thursday 16 February 2006 11:09, François-Xavier Coudert wrote:
> > Hi all,
> >
> > I'm sending this mail because I'm a bit confused about the
> > -mlong-double-128 option on (for example) ppc64-linux, and its impact
> > on gfortran/libgfortran
On Thursday 16 February 2006 15:14, François-Xavier Coudert wrote:
> > Having gfortran magically know about certain ABI breaking options, and
> > doing funny things on certain targets seems a very bad precedent to me.
>
> Then, I think we should have the front-end refuse the option. It's
> annoying
On 2/16/06, Jakub Jelinek <[EMAIL PROTECTED]> wrote:
> On Thu, Feb 16, 2006 at 01:57:39PM +0100, Fran?ois-Xavier Coudert wrote:
> > > I guess libgfortran has configury to figure out if kind=16 is available?
> >
> > Yes.
> >
> > > If so then libgfortran should be built with -mlong-double-128, as thi
> Having gfortran magically know about certain ABI breaking options, and doing
> funny things on certain targets seems a very bad precedent to me.
Then, I think we should have the front-end refuse the option. It's
annoying to have a compiler accept code, and only tell you at runtime
(at the end of
On Thursday 16 February 2006 11:09, François-Xavier Coudert wrote:
> Hi all,
>
> I'm sending this mail because I'm a bit confused about the
> -mlong-double-128 option on (for example) ppc64-linux, and its impact
> on gfortran/libgfortran.
>
> When I simply bootstrap a compiler with "configure
> --w
On Thu, Feb 16, 2006 at 01:57:39PM +0100, Fran?ois-Xavier Coudert wrote:
> > I guess libgfortran has configury to figure out if kind=16 is available?
>
> Yes.
>
> > If so then libgfortran should be built with -mlong-double-128, as this
> > should only add extra symbols that do not conflict with k
> I guess libgfortran has configury to figure out if kind=16 is available?
Yes.
> If so then libgfortran should be built with -mlong-double-128, as this
> should only add extra symbols that do not conflict with kind=4 and kind=8
> ones.
Hum, that has to be done early in the configury (before all
On 2/16/06, François-Xavier Coudert <[EMAIL PROTECTED]> wrote:
> Hi all,
>
> I'm sending this mail because I'm a bit confused about the
> -mlong-double-128 option on (for example) ppc64-linux, and its impact
> on gfortran/libgfortran.
>
> When I simply bootstrap a compiler with "configure
> --with-
11 matches
Mail list logo
