On Sun, 2008-06-01 at 00:07 -0700, Patrick McCarty wrote:
> On Sat, May 31, 2008 at 10:29 PM, Joe Neeman <[EMAIL PROTECTED]> wrote:
> >
> > What if you change __x86__ to __i386__? (Sorry to turn you into a guinea
> > pig, but I don't have an array of different x86 configurations at my
> > disposal)
On Sat, May 31, 2008 at 10:29 PM, Joe Neeman <[EMAIL PROTECTED]> wrote:
>
> What if you change __x86__ to __i386__? (Sorry to turn you into a guinea
> pig, but I don't have an array of different x86 configurations at my
> disposal).
Great! Changing it to __i386__ works for me. Thanks a lot, Joe!
On Sat, 2008-05-31 at 21:11 -0700, Patrick McCarty wrote:
> On Sat, May 31, 2008 at 8:30 PM, Joe Neeman <[EMAIL PROTECTED]> wrote:
> > On Sat, 2008-05-31 at 20:20 -0700, Patrick McCarty wrote:
> >>
> >> Hi Joe,
> >>
> >> I am still experiencing this infinite loop after your fix. However,
> >> if I
On Sat, May 31, 2008 at 8:30 PM, Joe Neeman <[EMAIL PROTECTED]> wrote:
> On Sat, 2008-05-31 at 20:20 -0700, Patrick McCarty wrote:
>>
>> Hi Joe,
>>
>> I am still experiencing this infinite loop after your fix. However,
>> if I remove the #ifdef structure and keep the function and function
>> call,
On Sat, 2008-05-31 at 20:20 -0700, Patrick McCarty wrote:
> On Wed, May 28, 2008 at 3:15 PM, Joe Neeman <[EMAIL PROTECTED]> wrote:
> > On Wed, 2008-05-28 at 11:02 -0300, Han-Wen Nienhuys wrote:
> >> Could someone put this into a init_fpu() function with appropriate
> >> #ifdefs, and call that from
On Wed, May 28, 2008 at 3:15 PM, Joe Neeman <[EMAIL PROTECTED]> wrote:
> On Wed, 2008-05-28 at 11:02 -0300, Han-Wen Nienhuys wrote:
>> Could someone put this into a init_fpu() function with appropriate
>> #ifdefs, and call that from main() ?
>
> Done.
Hi Joe,
I am still experiencing this infinite
On Wed, 2008-05-28 at 11:02 -0300, Han-Wen Nienhuys wrote:
> Could someone put this into a init_fpu() function with appropriate
> #ifdefs, and call that from main() ?
Done.
>
>
> Thanks!
>
> 2008/5/28 John Mandereau <[EMAIL PROTECTED]>:
> > On 2008/05/26, I wrote:
> >> #include
> >> and addin
Could someone put this into a init_fpu() function with appropriate
#ifdefs, and call that from main() ?
Thanks!
2008/5/28 John Mandereau <[EMAIL PROTECTED]>:
> On 2008/05/26, I wrote:
>> #include
>> and adding the two lines
>>
>> fpu_control_t fpu_control = 0x027f ;
>> _FPU_SETCW(fpu_contro
On 2008/05/26, I wrote:
> #include
> and adding the two lines
>
> fpu_control_t fpu_control = 0x027f ;
> _FPU_SETCW(fpu_control);
>
> at the beginning of main(). This fixes the bug for me with GCC 4.3.0 on
> Joe's example skyline2.cc
This fix works on my Celeron M with current Lily on mast
On 2008/05/26, Joe Neeman wrote:
> Attached is the smallest example that I could find that reproduces the
> problem. With g++ 4.3.0 on Fedora 9, I get an infinite loop with -O1 but
> immediate termination with -O0. With g++ 4.2.3 on Debian, I get
> termination regardless of the optimisation setting
On Sun, 2008-05-25 at 13:41 +0200, John Mandereau wrote:
> On 2008/05/23, Joe Neeman wrote:
> > Does re-building without optimisations help?
>
> Yes, it does! Building with GCC 4.3.0 and without -O2 flag makes
> LilyPond produce the same output [*] as with GCC 4.1.2 with
> optimisations, but it i
On 2008/05/23, Joe Neeman wrote:
> Does re-building without optimisations help?
Yes, it does! Building with GCC 4.3.0 and without -O2 flag makes
LilyPond produce the same output [*] as with GCC 4.1.2 with
optimisations, but it is also (not very surpisingly) much slower, so
I'll go on building Lil
2008/5/19 John Mandereau <[EMAIL PROTECTED]>:
> Hi,
>
> I just installed Fedora 9 on my x86 (32 bits) laptop, which comes with
> gcc (GCC) 4.3.0 20080428 (Red Hat 4.3.0-8).
>
> I can compile LilyPond binary succesfully, but running it on any input
> file makes it hang on an infinite loop, most oft
Hi,
I just installed Fedora 9 on my x86 (32 bits) laptop, which comes with
gcc (GCC) 4.3.0 20080428 (Red Hat 4.3.0-8).
I can compile LilyPond binary succesfully, but running it on any input
file makes it hang on an infinite loop, most often after Preprocessing
graphical objects; every Control-C i
14 matches
Mail list logo