[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: Coverity Scan for GNUstep?
From: |
David Chisnall |
Subject: |
Re: Coverity Scan for GNUstep? |
Date: |
Thu, 25 Jan 2018 09:20:23 +0000 |
On 24 Jan 2018, at 23:56, Ivan Vučica <address@hidden> wrote:
>
> Even though it's just silencing this warning, I'm nonetheless creating
> a patch for gdomap.
It isn’t just silencing the warning, it’s also generating smaller code. When
calling a function that doesn’t return, the compiler doesn’t have to emit any
code to handle the return path - no registers or stack slots are going to be
live after the call and so it doesn’t have to bother saving anything. It
probably only saves 2-3 instructions at most call sites, but across a few
hundred calling locations that can add up to a lot.
David
- Re: Coverity Scan for GNUstep?, (continued)
- Re: Coverity Scan for GNUstep?, Patryk Laurent, 2018/01/21
- Re: Coverity Scan for GNUstep?, Fred Kiefer, 2018/01/22
- Re: Coverity Scan for GNUstep?, Ivan Vučica, 2018/01/24
- Re: Coverity Scan for GNUstep?, Ivan Vučica, 2018/01/24
- Re: Coverity Scan for GNUstep?, Fred Kiefer, 2018/01/25
- Re: Coverity Scan for GNUstep?, Richard Frith-Macdonald, 2018/01/25
- Re: Coverity Scan for GNUstep?,
David Chisnall <=
- Re: Coverity Scan for GNUstep?, Richard Frith-Macdonald, 2018/01/29
- Re: Coverity Scan for GNUstep?, Fred Kiefer, 2018/01/29
- Re: Coverity Scan for GNUstep?, Richard Frith-Macdonald, 2018/01/29
- Re: Coverity Scan for GNUstep?, Ivan Vučica, 2018/01/29
- Re: Coverity Scan for GNUstep?, Fred Kiefer, 2018/01/29
- Re: Coverity Scan for GNUstep?, Wolfgang Lux, 2018/01/29
- Re: Coverity Scan for GNUstep?, Fred Kiefer, 2018/01/29
- Re: Coverity Scan for GNUstep?, Fred Kiefer, 2018/01/30
Re: Coverity Scan for GNUstep?, Richard Frith-Macdonald, 2018/01/15