Skip to content
New issue

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

Jump to bottom

FB3.0 RC1 Fbclient.dll function calls modify FPU control word [CORE5102] #5386

Closed
firebird-automations opened this issue Feb 3, 2016 · 5 comments
Closed

FB3.0 RC1 Fbclient.dll function calls modify FPU control word [CORE5102] #5386

firebird-automations opened this issue Feb 3, 2016 · 5 comments
Assignees
@hvlad
Labels
affect-version: 3.0 RC1 component: api / client library fix-version: 3.0 RC2 priority: minor qa: cannot be tested type: bug

Comments

@firebird-automations
Copy link
Collaborator

Submitted by: michalk1 (michalk1)

This is almost similar to CORE4043, which was fixed in 2.5.3. In FB3 RC1, FPU returns with all flags masked, ie:

before call 1 00 11 00 110010 (0x1332)
after call 1 00 11 01 111111 (0x137F)

All remote functions seem to be affected (isc_attach_database, isc_dsql_execute2, isc_dsql_fetch, isc_dsql_free_statement, isc_commit_transaction, isc_service_start etc.)

Commits: f3402ca FirebirdSQL/fbt-repository@826666d
@firebird-automations
Copy link
Collaborator Author

Modified by: @hvlad

assignee: Vlad Khorsun [ hvlad ]

@firebird-automations
Copy link
Collaborator Author

Commented by: @hvlad

Code from v2.5 is frontported, please verify

@firebird-automations
Copy link
Collaborator Author

Commented by: michalk1 (michalk1)

I just tested fbclient.dll from the current snapshot build (WI-V3.0.0.32320), and the problem is gone, fpu control word now remains constant. Thanks.

@firebird-automations
Copy link
Collaborator Author

Modified by: @hvlad

status: Open [ 1 ] => Resolved [ 5 ]

resolution: Fixed [ 1 ]

Fix Version: 3.0 RC2 [ 10048 ]

@firebird-automations
Copy link
Collaborator Author

Modified by: @pavel-zotov

status: Resolved [ 5 ] => Resolved [ 5 ]

QA Status: No test => Cannot be tested

@mikerabat mikerabat mentioned this issue Sep 22, 2023
Closed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@hvlad hvlad

Labels
affect-version: 3.0 RC1 component: api / client library fix-version: 3.0 RC2 priority: minor qa: cannot be tested type: bug
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@hvlad @firebird-automations