Skip to content

[GAP] Always build with GCC, even on macOS#13274

Merged
fingolfin merged 1 commit intomasterfrom
mh/GAP
Mar 11, 2026
Merged

[GAP] Always build with GCC, even on macOS#13274
fingolfin merged 1 commit intomasterfrom
mh/GAP

Conversation

@fingolfin
Copy link
Member

This allows Base.stacktrace() from inside GAP to traverse back into Julia code. This will allow us to produce much more helpful backtraces in GAP.jl.

Note that GAP does not link against the C++ standard library, does not use C++ exceptions, or expose or consume any C++ ABIs. So I think this should be fine without applying a similar treatment to GAP packages which use C++, such as semigroups or normalizinterface.

@lgoettgens
Copy link
Collaborator

Note that GAP does not link against the C++ standard library, does not use C++ exceptions, or expose or consume any C++ ABIs. So I think this should be fine without applying a similar treatment to GAP packages which use C++, such as semigroups or normalizinterface.

What about GAP_pkg_juliainterface? Doesn't that show up in some stacktraces?

@fingolfin
Copy link
Member Author

True, but so far it wasn't problematic. Even if it is, it can be rebuilt separately later on. This change here is the big one (for macOS; on Linux things are already in a good shape)

Copy link
Collaborator

@lgoettgens lgoettgens left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Seems reasonable, but I haven't tested it locally

@lgoettgens
Copy link
Collaborator

Would it make sense to bump the version number, so you can require a newer version in you dev branch of GAP.jl?

@fingolfin
Copy link
Member Author

good point, will do

This allows Base.stacktrace() from inside GAP to traverse back
into Julia code.
@fingolfin fingolfin enabled auto-merge (squash) March 11, 2026 13:30
@fingolfin fingolfin merged commit 63338af into master Mar 11, 2026
14 checks passed
@fingolfin fingolfin deleted the mh/GAP branch March 11, 2026 13:44
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