force gcc optimization to O1 in KWDGPODiscretizer #238
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
bruno-at-orange
force-pushed
the
163-segmentation-fault-of-coclustering-on-debian-12
branch
3 times, most recently
from
b9c81cd to
d3edbad
Compare
With gcc 12.2.0 (on debian 12), gcc seems too agressive. The only way to fix a segmentation fault is to force the optimization level to O1 instead of O2. The segmentation fault occured while accessing the variable cell1 which is NULL. By adding the following (unnecessary) line, the segmentation fault vanishes: if (cell1==NULL or cell2==NULL) exit(1);
bruno-at-orange
force-pushed
the
163-segmentation-fault-of-coclustering-on-debian-12
branch
from
d3edbad to
bfc01f0
Compare
marcboulle
approved these changes
Apr 16, 2024
bruno-at-orange
deleted the
163-segmentation-fault-of-coclustering-on-debian-12
branch
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
With gcc 12.2.0 (on debian 12), gcc seems too aggressive. The only way to fix a segmentation fault is to force the optimization level to O1 instead of O2.
The segmentation fault occurred while accessing the variable cell1 which is NULL. By adding the following (unnecessary) line, the segmentation fault vanishes:
With O1 optimization level, this line is not necessary to cope with this segmentation fault
close #163