Seems to work correctly now. Thanks.
On Feb 5, 2008, at 2:26 AM, Slava Pestov wrote:
Hi,
This is now fixed in the latest git.
Slava
-
This SF.net email is sponsored by: Microsoft
Defy all challenges. Microsoft(R)
Hi,
This is now fixed in the latest git.
Slava
Jorge Acereda Maciá wrote:
I think I'm facing a bug in Factor. I have something like this:
TYPEDEF: double PaTime
C-STRUCT: PaDeviceInfo
{ int structVersion }
{ char* name }
{ PaHostApiIndex hostApi }
{ int
It seems it's an alignment problem. gcc doesn't seem to align the
double fields to 8 bytes under x86, and factor seems to enforce 8
bytes alignment for doubles. Am I right?
On Sat, Jan 26, 2008 at 9:52 PM, Jorge Acereda [EMAIL PROTECTED] wrote:
Forgot to say that I'm using the git version on a
Jorge Acereda wrote:
It seems it's an alignment problem. gcc doesn't seem to align the
double fields to 8 bytes under x86, and factor seems to enforce 8
bytes alignment for doubles. Am I right?
Sounds possible. I'll investigate.
Slava
I think I'm facing a bug in Factor. I have something like this:
TYPEDEF: double PaTime
C-STRUCT: PaDeviceInfo
{ int structVersion }
{ char* name }
{ PaHostApiIndex hostApi }
{ int maxInputChannels }
{ int maxOutputChannels }
{ PaTime defaultLowInputLatency }
