On Thu, Jul 28, 2022 at 08:53:37PM +0100, Jonathan Wakely via Gcc wrote:
> On Thu, 28 Jul 2022 at 20:49, Tim Lange wrote:
> >
> >
> >
> > On Thu, Jul 28 2022 at 02:46:58 PM -0400, David Malcolm via Gcc
> > wrote:
> > > Is there documentation on setting up text editors to work with our
> > > coding
On 7/28/22 21:49, Tim Lange wrote:
>
>
> On Thu, Jul 28 2022 at 02:46:58 PM -0400, David Malcolm via Gcc
> wrote:
>> Is there documentation on setting up text editors to work with our
>> coding style? A lot of the next generation of developers aren't using
>> vi or emacs; they's using VS Code,
On Mon, 1 Aug 2022 at 09:24, Stefan Schulze Frielinghaus wrote:
> I gave unexpand from GNU coreutils 8.32 a try. Looks like it cannot
> deal with form feeds or maybe I'm missing something?
>
> $ bash -c "printf 'foo\n\f\nbar\n'" | unexpand -
> foo
> unexpand: input line is too long
Which
On Mon, Aug 01, 2022 at 12:25:21PM +0100, Jonathan Wakely wrote:
> On Mon, 1 Aug 2022 at 09:24, Stefan Schulze Frielinghaus wrote:
> > I gave unexpand from GNU coreutils 8.32 a try. Looks like it cannot
> > deal with form feeds or maybe I'm missing something?
> >
> > $ bash -c "printf 'foo\n\f\n
rajaraju6...@gmail.co
On Mon, 1 Aug 2022 at 13:16, Stefan Schulze Frielinghaus wrote:
>
> On Mon, Aug 01, 2022 at 12:25:21PM +0100, Jonathan Wakely wrote:
> > On Mon, 1 Aug 2022 at 09:24, Stefan Schulze Frielinghaus wrote:
> > > I gave unexpand from GNU coreutils 8.32 a try. Looks like it cannot
> > > deal with form fe
Dear developers,
May I seek your confirmation to check whether the following program
triggers a true wrong-code issue in GCC? The following piece of code looks
too simple and I am not quite sure whether it's a bug or not.
Here is the test program (s.c):
```
int a = 0, b = 0;
int main() {
for (; a
Oh, sorry for the noise, there is an integer overflow that may cause
undefined behavior.
Haoxin Tu 于2022年8月2日周二 11:23写道：
> Dear developers,
>
> May I seek your confirmation to check whether the following program
> triggers a true wrong-code issue in GCC? The following piece of code looks
> too s
On Tue, 2 Aug 2022 at 05:45, Haoxin Tu via Gcc wrote:
>
> Oh, sorry for the noise, there is an integer overflow that may cause
> undefined behavior.
You should check with UBsan before reporting something as a bug:
s.c:5:2: runtime error: signed integer overflow: 2147483647 + 1 cannot
be represen
