[GHC] #15068: Small number of test case failures on Ubuntu Bionic (GCC 7.3)

[GHC]

#15068: Small number of test case failures on Ubuntu Bionic (GCC 7.3)
-------------------------------------+-------------------------------------
        Reporter:  jrp               |                Owner:  (none)
            Type:  bug               |               Status:  merge
        Priority:  highest           |            Milestone:  8.6.1
       Component:  Compiler          |              Version:  8.4.1
  (CodeGen)                          |
      Resolution:  fixed             |             Keywords:
Operating System:  Linux             |         Architecture:  x86_64
                                     |  (amd64)
 Type of failure:  Incorrect result  |            Test Case:  T13658
  at runtime                         |  T14779a T14779b T14868 debug
                                     |  parsing001
      Blocked By:                    |             Blocking:
 Related Tickets:                    |  Differential Rev(s):  Phab:D4654
       Wiki Page:                    |
-------------------------------------+-------------------------------------

Comment (by recursion-ninja):

 I don't want to spam the GHC maintainers who get emails for updates on
 tickets. However, I think it's important to note that the non-`stack`
 users affected by this defect may not be so esoteric.

 Replying to [comment:33 hvr]:
 > Finally, this doesn't affect non-Stack users, unless they are on a just
 released Ubuntu 18 release (NB: there's currently 3 LTS releases of Ubuntu
 that aren't EOL'ed; nobody is forced to use the still very infantly young
 new Ubuntu LTS yet) ...

 I was having "show-stopping" graphics driver issues on Ubuntu 16.04 that
 were only resolved by the 4.15.* version of the Linux kernel which was not
 and would not be supported (to the best of my knowledge) by Ubuntu 16.04.
 My upgrade to Ubuntu 18.04 was more or less "forced" to get a kernel
 version compatible with my machine.


 Replying to [comment:33 hvr]:
 > ... *and* use a non-default flag which is only relevant if you actually
 intend and know how to debug a Haskell program at a low-level via a
 debugger such as GDB.

 I was passing the `-g` flag while building with `cabal` because I have
 been fixing a defective feature involving the `Cabal` library linking to C
 & C++ sources and required debugging symbols while investigating and
 correcting the issue. https://github.com/haskell/cabal/pull/5315


 Replying to [comment:33 hvr]:
 > I seriously doubt this is a large enough group of people to demand this
 urgency.

 This might be true. However, I did encountered this `-g` related defect
 through "normal," non-`stack` usage of `ghc`. There's a chance that my
 situation is an anomaly, but there's also a chance the defect might have a
 larger impact than estimated.

-- 
Ticket URL: <http://ghc.haskell.org/trac/ghc/ticket/15068#comment:37>
GHC <http://www.haskell.org/ghc/>
The Glasgow Haskell Compiler