[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

PSPP-BUG: [bug #58943] Test 127 "zero or one variable in mrset" fails on

From: Friedrich Beckmann
Subject: PSPP-BUG: [bug #58943] Test 127 "zero or one variable in mrset" fails on debian/bullseye with -O2 -g optimization
Date: Thu, 13 Aug 2020 08:54:21 -0400 (EDT)
User-agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10_13_6) AppleWebKit/605.1.15 (KHTML, like Gecko) Version/13.1.2 Safari/605.1.15


                 Summary: Test 127 "zero or one variable in mrset" fails on
debian/bullseye with -O2 -g optimization
                 Project: PSPP
            Submitted by: beckmanf
            Submitted on: Thu 13 Aug 2020 12:54:19 PM UTC
                Category: Compilation/Portability
                Severity: 5 - Average
                  Status: None
             Assigned to: None
             Open/Closed: Open
                 Release: None
         Discussion Lock: Any
                  Effort: 0.00



The current pspp git master on commit e45cdf7b0e1b1b fails on debian/bullseye
in test 127 when pspp is compiled with opimization "-O2 -g". 

The failed test "testing zero or one variable in mrset " produces the
following output:

#                             -*- compilation -*-
127. sys-file-reader.at:2780: testing zero or one variable in mrset ...
../../pspp/tests/sys-file-reader.at:2799: sack --$variant sys-file.sack >
../../pspp/tests/sys-file-reader.at:2802: pspp -O format=csv sys-file.sps
--- -   2020-08-13 14:17:37.563145916 +0200
+++ /home/fritz/pspp/build/tests/testsuite.dir/at-groups/127/stdout    
2020-08-13 14:17:37.555867407 +0200
@@ -1,3 +1,5 @@
+warning: `sys-file.sav' near offset 0xd8: Missing new-line parsing variable
names at offset 22 in MRSETS record.
 warning: `sys-file.sav': MRSET $a has only one variable.
 warning: `sys-file.sav': MRSET $b has no variables.
127. sys-file-reader.at:2780: 127. zero or one variable in mrset
(sys-file-reader.at:2780): FAILED (sys-file-reader.at:2802)

The test succeeds when the compiler setting is changed to "-O0 -g". The same
happens on the 1.2.0 release. There were reports about the same failed test
for 1.2.0 on ppc64el architecture when compiled with "-O3" from Steve


That was fixed by changing the optimization to "-O2". Now we have this problem
on amd64 when compiler optimization is "-O2". Either it is a compiler bug or
we have some unconventional code...

The sack seems to be o.k. because I can read the produced sys-file.sav file
with a "-O0 -g" pspp version and the result is o.k. 

The gcc compiler version on debian/bullseye is: gcc (Debian 10.1.0-6) 10.1.0
but the problem report on ppc64el was with gcc-8.


Reply to this item at:


  Message sent via Savannah

reply via email to

[Prev in Thread] Current Thread [Next in Thread]