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

Memory alignment problem with unique expression index [CORE3941] #4274

Closed
firebird-issue-importer opened this issue Sep 27, 2012 · 6 comments

Comments

@firebird-issue-importer

Submitted by: @asfernandes

A memory aligment problem may cause slow performance on x86/amd64 and malfunction in others architectures.

Commits: c295605

@firebird-issue-importer
Copy link
Author

firebird-issue-importer commented Sep 27, 2012

Modified by: @asfernandes

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

resolution: Fixed [ 1 ]

Fix Version: 3.0 Alpha 1 [ 10331 ]

assignee: Adriano dos Santos Fernandes [ asfernandes ]

@firebird-issue-importer
Copy link
Author

firebird-issue-importer commented Sep 28, 2012

Commented by: @hvlad

Why not backport it into 2.5.3\2.1.6 ?

@firebird-issue-importer
Copy link
Author

firebird-issue-importer commented Sep 29, 2012

Commented by: @asfernandes

1) The issue was reported by nobody. I just saw it reading the code.
2) It may not even exist in real world. In my test, the variable was correctly aligned on the stack.
3) It's not a severe problem on x86. If nobody from others platforms reported it, it means nobody is using it or the compiler aligned it correctly.

@firebird-issue-importer
Copy link
Author

firebird-issue-importer commented Apr 23, 2013

Modified by: @pcisar

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

@firebird-issue-importer
Copy link
Author

firebird-issue-importer commented Jan 18, 2016

Modified by: @pavel-zotov

status: Closed [ 6 ] => Closed [ 6 ]

QA Status: No test

@firebird-issue-importer
Copy link
Author

firebird-issue-importer commented May 25, 2016

Modified by: @pavel-zotov

status: Closed [ 6 ] => Closed [ 6 ]

QA Status: No test => Cannot be tested

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment