We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
I'm porting an old amiga program
and when I created a sfd file with this Entry
void setlibtrig(doubles1,doubles2,doubles3,doublec1,doublec2,doublec3)(A0,A1,A2,D0,D1,D2)
It would fail when generation vbcc inlines with this command
fd2pragma --infile engine.sfd --to inline --special 70
After some debuging I found out that in
/* merge data register pairs for 64-bit argument types */ static void FindRegPairs(struct AmiPragma *ap, struct ClibData *cd)
it would handle it as a 64bit and try an alloc 2 regs for it..
so my temp fix was to add this too the IF check (in that function)
&& ( ! cd->Args[i].Flags & CPP_FLAG_POINTER )
Not sure if the correct way is
&& ( ! cd->Args[i].Flags & (CPP_FLAG_POINTER|CPP_FLAG_FUNCTION ))
Regards René W. Olsen
The text was updated successfully, but these errors were encountered:
No branches or pull requests
I'm porting an old amiga program
and when I created a sfd file with this Entry
void setlibtrig(doubles1,doubles2,doubles3,doublec1,doublec2,doublec3)(A0,A1,A2,D0,D1,D2)
It would fail when generation vbcc inlines with this command
fd2pragma --infile engine.sfd --to inline --special 70
After some debuging I found out that in
/* merge data register pairs for 64-bit argument types */
static void FindRegPairs(struct AmiPragma *ap, struct ClibData *cd)
it would handle it as a 64bit and try an alloc 2 regs for it..
so my temp fix was to add this too the IF check (in that function)
&& ( ! cd->Args[i].Flags & CPP_FLAG_POINTER )
Not sure if the correct way is
&& ( ! cd->Args[i].Flags & (CPP_FLAG_POINTER|CPP_FLAG_FUNCTION ))
Regards
René W. Olsen
The text was updated successfully, but these errors were encountered: