Avoid calling ConvertToVectorRep(v, 0) #4107
Closed
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.
The family of finite fields of size >= 256 sets
!.rchar = 0, which leads to calls of 'ConvertToVectorRep'
with second argument 0 in various places.
Added a test which demonstrates the problem.
Description
The problem is described above.
The bug addressed here can be seen in this example:
I'm not sure, if this pull request catches all instances of the problem. It is at least a quick fix which should never be bad.
A better fix would probably try to avoid that for larger finite fields its family has a component
!.rchar
which is set to0
(instead of the characteristic of the field).Text for release notes
A bug in the arithmetic of larger finite fields was fixed.