https://gcc.gnu.org/bugzilla/show_bug.cgi?id=99210
Jerry DeLisle changed:
What|Removed |Added
Resolution|--- |FIXED
Status|NEW
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=99210
--- Comment #8 from GCC Commits ---
The master branch has been updated by Jerry DeLisle :
https://gcc.gnu.org/g:b79d3e6a9284703b70688122f7d4955e7c50804a
commit r14-8983-gb79d3e6a9284703b70688122f7d4955e7c50804a
Author: Jerry DeLisle
Date: Tu
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=99210
--- Comment #7 from Jerry DeLisle ---
Submitted for approval.
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=99210
--- Comment #6 from Jerry DeLisle ---
I have reapplied the patch in comment #3 and it regression tests fine and
appears to fix the issue. I have need to work up the test case and submit this
for approval.
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=99210
Jerry DeLisle changed:
What|Removed |Added
Assignee|unassigned at gcc dot gnu.org |jvdelisle at gcc dot
gnu.org
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=99210
--- Comment #4 from Jerry DeLisle ---
I think the patch works fine as is as far as I can tell. There will be a
similar fix for writing files with encoding='utf8'
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=99210
Jerry DeLisle changed:
What|Removed |Added
Status|ASSIGNED|NEW
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=99210
--- Comment #3 from Jerry DeLisle ---
Here is the real issue. The X format specifier is a position modifier. UTF-8 is
a variable character length encoding so moving one character could mean move 1,
2, 3, or 4 bytes depending on the content of the
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=99210
Jerry DeLisle changed:
What|Removed |Added
Last reconfirmed||2021-02-23
CC|
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=99210
Serguei E. Leontiev changed:
What|Removed |Added
CC||leo at sai dot msu.ru
--- Comment
10 matches
Mail list logo
