Tcl Source Code

View Ticket
Login
2021-12-08
15:54 • Closed ticket [206e58994f]: tcl builds with clang but fails to run correctly... artifact: abf7334235 user: jan.nijtmans
2021-12-05
08:38 • Ticket [206e58994f]: 3 changes artifact: 309347677f user: chrstphrchvz
2021-12-02
21:41 • Add attachment build.log to ticket [206e58994f] artifact: 20fc71deca user: dilfridge
21:38 • New ticket [206e58994f] tcl builds with clang but fails to run correctly. artifact: 71a0ac08b2 user: dilfridge

Ticket UUID: 206e58994f3806ec880a59ecc516ee632cd89424
Title: tcl builds with clang but fails to run correctly
Type: Bug Created on: 2021-12-02 21:38:26
Submitter: dilfridge Assigned to: jan.nijtmans
Subsystem: 69. Other Severity: Critical
Priority: 5 Medium Last modified: 2021-12-08 15:54:55
Status: Closed Closed by: jan.nijtmans
Resolution: Fixed Closed on: 2021-12-08 15:54:55
Version: 8.6.11
Description:
The same build which produces a fully functional tcl using gcc also succeeds when using clang, but the resulting binary produces erratic results. 

chan.test prints a lot of failures and eventually hangs. Random example: 



==== chan-io-3.5 WriteChars: saved != 0 FAILED
==== Contents of test case:

    # Bytes produced by UtfToExternal from end of last channel buffer had to
    # be moved to beginning of next channel buffer to preserve requested
    # buffersize.
    set f [open $path(test1) w]
    chan configure $f -encoding jis0208 -buffersize 17
    chan puts -nonewline $f "\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\"
    set x [list [contents $path(test1)]]
    chan close $f
    lappend x [contents $path(test1)]

---- Result was:
!)!)!)!)!)!)!)!)! !)!)!)!)!)!)!)!)!!)!)!)!)!)!)!
---- Result should have been (exact matching):
!)!)!)!)!)!)!)!)! !)!)!)!)!)!)!)!)!)!)!)!)!)!)!)
==== chan-io-3.5 FAILED
User Comments:
chrstphrchvz added on 2021-12-05 08:38:34:

Is the reporter is using LLVM Clang 13 or newer? If so, is this issue a duplicate of [24b9181478], i.e. fixed in Tcl 8.6.12?


jan.nijtmans added on 2021-12-08 15:54:55:
Yes, this looks exactly like a duplicate of [24b9181478]. Closing.

@dilfridge, if you still find this problem - somehow - in 8.6.12, please re-open this ticket.

Attachments: