bitwiseworks/gcc-os2
1
0
Fork 0
mirror of https://github.com/bitwiseworks/gcc-os2.git synced 2026-02-14 06:04:44 +00:00
Code Issues 22 Packages Projects Releases Wiki Activity

Investigate why alignas(8) doesn't always work #36

New Issue
Closed
opened 2026-01-29 22:24:07 +00:00 by claunia · 2 comments
claunia commented 2026-01-29 22:24:07 +00:00
Owner
Copy Link

Originally created by @dmik on GitHub (Aug 28, 2020).

As Chromium tests show (see https://github.com/bitwiseworks/qtwebengine-chromium-os2/issues/20#issue-686420732), alignas(8) is not always respected by GCC when allocating variables on the stack. Most of the time it works (i.e. variables get stack addresses ending with either 0x0 or 0x8) but occasionally something breaks and variables end up at "odd" addresses ending with 0x4 or 0xC. The Mojo component in Chromium is pretty strict about that and crashes the application on alignment mismatch.

Originally created by @dmik on GitHub (Aug 28, 2020). As Chromium tests show (see https://github.com/bitwiseworks/qtwebengine-chromium-os2/issues/20#issue-686420732), `alignas(8)` is not always respected by GCC when allocating variables on the stack. Most of the time it works (i.e. variables get stack addresses ending with either 0x0 or 0x8) but occasionally something breaks and variables end up at "odd" addresses ending with 0x4 or 0xC. The Mojo component in Chromium is pretty strict about that and crashes the application on alignment mismatch.
claunia commented 2026-01-29 22:24:09 +00:00
Author
Owner
Copy Link

@dmik commented on GitHub (Aug 28, 2020):

Note that I could not reproduce it in a simple test case. The problem can only be observed within the huge Chromium context so far.

@dmik commented on GitHub (Aug 28, 2020): Note that I could not reproduce it in a simple test case. The problem can only be observed within the huge Chromium context so far.
claunia commented 2026-01-29 22:24:12 +00:00
Author
Owner
Copy Link

@dmik commented on GitHub (Jun 30, 2023):

Actually, we already have another ticket for this task, #11. Closing this in favour of that.

@dmik commented on GitHub (Jun 30, 2023): Actually, we already have another ticket for this task, #11. Closing this in favour of that.
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
postponed
No Label
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
claunia
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: bitwiseworks/gcc-os2#36
Delete Branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?