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

testbed: make header alignment a bit more reliable #1

Closed
wants to merge 1 commit into from
Closed

testbed: make header alignment a bit more reliable #1

wants to merge 1 commit into from

Conversation

trofi
Copy link

@trofi trofi commented Aug 12, 2011

Hia!

I've debugged BUS error for test on sparc today. Yeah, I've seen it's fixed by latest commit,
but I've decided to clean it a bit to make more stable to further changes.

If you ever decide to add even larger alignment requirements like 'long double',
or something even wider like SSE-aligned bits - you'll just need to add bigger type
to union.

Thanks!

Signed-off-by: Sergei Trofimovich <slyfox@gentoo.org>
@mm2
Copy link
Owner

mm2 commented Aug 13, 2011

Excellent! thank you so much, I'm adding your changes to the master
repository

Best regards
Marti

Original Message:

From: trofi
reply@reply.github.com
Date: Fri, 12 Aug 2011 11:12:58 -0700
To: marti.maria@littlecms.com
Subject: [Little-CMS] testbed: make header alignment a bit more reliable
(#1)

Hia!

I've debugged BUS error for test on sparc today. Yeah, I've seen it's fixed
by latest commit,
but I've decided to clean it a bit to make more stable to further changes.

If you ever decide to add even larger alignment requirements like 'long
double',
or something even wider like SSE-aligned bits - you'll just need to add
bigger type
to union.

Thanks!

Reply to this email directly or view it on GitHub:
#1


mail2web.com � What can On Demand Business Solutions do for you?
http://link.mail2web.com/Business/SharePoint

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants