Hello t7,
* t66...@gmail.com wrote on Thu, Sep 23, 2010 at 03:01:31AM CEST:
> I don't know if my problem suites this description.
No, it doesn't.
> Currently installed libtool on this system is,
> ltmain.sh (GNU libtool) 2.2.6b
>
> I recently tested the LTO feature of GCC (targeting windows
Hello all,
I don't know if my problem suites this description.
On 31/03/2010 6:52 AM, Ralf Wildenhues wrote:
Hello gcc and libtool lists,
Summary: both Autoconf-generated configure tests as well as some Libtool
construct invoke undefined behavior. Question is how to deal with it,
and whether GC
On Wed, Mar 31, 2010 at 8:33 PM, Ralf Wildenhues wrote:
> * Richard Guenther wrote on Wed, Mar 31, 2010 at 11:02:39AM CEST:
>> On Tue, Mar 30, 2010 at 8:52 PM, Ralf Wildenhues wrote:
>> > 1) Autoconf-generated configure tests often fake the prototype of some
>> > function; e.g., AC_CHECK_FUNC([fun
* Richard Guenther wrote on Wed, Mar 31, 2010 at 11:02:39AM CEST:
> On Tue, Mar 30, 2010 at 8:52 PM, Ralf Wildenhues wrote:
> > 1) Autoconf-generated configure tests often fake the prototype of some
> > function; e.g., AC_CHECK_FUNC([func]) uses
> > char func();
> >
> > and tries to link that. Us
On Tue, Mar 30, 2010 at 8:52 PM, Ralf Wildenhues wrote:
> Hello gcc and libtool lists,
>
> Summary: both Autoconf-generated configure tests as well as some Libtool
> construct invoke undefined behavior. Question is how to deal with it,
> and whether GCC, as QoI, may want to define behavior in the
