alloca (0) in include/libiberty.h

2019-06-10 Thread Martin Liška
Hi. I've just noticed that we have couple of alloca (0) in libiberty: #ifndef REGEX_MALLOC # ifdef C_ALLOCA alloca (0); # endif #endif If I'm correct the value 0 has a special meaning that tells a C library to clean up all previous alloca allocations. man alloca does not document the beha

Fire Sleeves for Protection of Cables and Wires

2019-06-10 Thread Ms Pooja 8928403615
FIRE SLEEVE FOR 1050ºC to 1650ºC Firesleeve (sometimes spelled fire sleeve or fire-sleeve) is the perfect sleeve and jacket choice for protecting industrial hydraulic hoses and lines, pneumatic lines, fuel & oil lines, brake lines, wires and cables from exposure to high temperature, heat, flam

Fire Sleeves for Protection of Cables and Wires

2019-06-10 Thread Ms Pooja 8928403615
FIRE SLEEVE FOR 1050ºC to 1650ºC Firesleeve (sometimes spelled fire sleeve or fire-sleeve) is the perfect sleeve and jacket choice for protecting industrial hydraulic hoses and lines, pneumatic lines, fuel & oil lines, brake lines, wires and cables from exposure to high temperature, heat, flam

Re: alloca (0) in include/libiberty.h

2019-06-10 Thread Andrew Haley
On 6/10/19 8:24 AM, Martin Liška wrote: > I've just noticed that we have couple of alloca (0) in libiberty: > > #ifndef REGEX_MALLOC > # ifdef C_ALLOCA > alloca (0); > # endif > #endif > > If I'm correct the value 0 has a special meaning that tells a C library > to clean up all previous al

Re: alloca (0) in include/libiberty.h

2019-06-10 Thread Jeff Law
On 6/10/19 5:54 AM, Andrew Haley wrote: > On 6/10/19 8:24 AM, Martin Liška wrote: > >> I've just noticed that we have couple of alloca (0) in libiberty: >> >> #ifndef REGEX_MALLOC >> # ifdef C_ALLOCA >> alloca (0); >> # endif >> #endif >> >> If I'm correct the value 0 has a special meaning t

Re: Preventing ISO C errors when using macros for builtin types

2019-06-10 Thread Jozef Lawrynowicz
On Wed, 5 Jun 2019 17:12:25 -0500 Segher Boessenkool wrote: > On Wed, Jun 05, 2019 at 08:49:39PM +0100, Jozef Lawrynowicz wrote: > > On Wed, 5 Jun 2019 11:49:21 -0500 > > Segher Boessenkool wrote: > > > The documentation says > > > > > > '-pedantic' and other options cause warnings for many

Re: Preventing ISO C errors when using macros for builtin types

2019-06-10 Thread Jozef Lawrynowicz
On Thu, 6 Jun 2019 10:09:32 +0200 Richard Biener wrote: > On Wed, Jun 5, 2019 at 3:26 PM Jozef Lawrynowicz wrote: > > > > I would appreciate if anyone can help me decide if: > > - It would be OK for the use of builtin macros such as __SIZE_TYPE__ to > > somehow > > not trigger the "pedantic e

Re: Preventing ISO C errors when using macros for builtin types

2019-06-10 Thread Segher Boessenkool
On Mon, Jun 10, 2019 at 05:20:31PM +0100, Jozef Lawrynowicz wrote: > On Thu, 6 Jun 2019 10:09:32 +0200 > Richard Biener wrote: > > > On Wed, Jun 5, 2019 at 3:26 PM Jozef Lawrynowicz > > wrote: > > > > > > I would appreciate if anyone can help me decide if: > > > - It would be OK for the use of

Re: Preventing ISO C errors when using macros for builtin types

2019-06-10 Thread Jozef Lawrynowicz
On Mon, 10 Jun 2019 13:32:42 -0500 Segher Boessenkool wrote: > On Mon, Jun 10, 2019 at 05:20:31PM +0100, Jozef Lawrynowicz wrote: > > On Thu, 6 Jun 2019 10:09:32 +0200 > > Richard Biener wrote: > > > > > On Wed, Jun 5, 2019 at 3:26 PM Jozef Lawrynowicz > > > wrote: > > > > > > > > I would

Re: About GSOC.

2019-06-10 Thread Joseph Myers
On Sun, 9 Jun 2019, Tejas Joshi wrote: > Hello. > I have created another patch which addresses the above points, > attached herewith. I don't think you should have the unreachable "return false;" in is_even. The last "else if" can just be "else". > > a conditional with < not <=; if REAL_EXP (r

Re: calling exit in response to an error shouldn't be an error...

2019-06-10 Thread L A Walsh
On 2019/06/09 14:52, Zan Lynx wrote: > I am not a GCC developer, just a regular user of C. But I have some > comments below: > > On 6/9/2019 3:21 PM, L A Walsh wrote: > >> If I have a function returning NULL on error (including EOF). >> >> So the program calls exit if the function doesn't retur

Re: calling exit in response to an error shouldn't be an error...

2019-06-10 Thread Jonathan Wakely
On Mon, 10 Jun 2019 at 22:54, L A Walsh wrote: > > On 2019/06/09 14:52, Zan Lynx wrote: > > I am not a GCC developer, just a regular user of C. But I have some > > comments below: > > > > On 6/9/2019 3:21 PM, L A Walsh wrote: > > > >> If I have a function returning NULL on error (including EOF). >

P.S. - Re: calling exit in response to an error shouldn't be an error...

2019-06-10 Thread L A Walsh
On 2019/06/09 14:52, Zan Lynx wrote: > I haven't tested it but you might be able to make this work with a comma > operator like "while (gets(buf) || (exit(0), 1)) puts(buf);" > yes, I also tried that to verify whether or not I needed a work-around for gets, though using "xit(int s){ exit(s);}"

Re: Preventing ISO C errors when using macros for builtin types

2019-06-10 Thread Segher Boessenkool
On Mon, Jun 10, 2019 at 08:58:00PM +0100, Jozef Lawrynowicz wrote: > On Mon, 10 Jun 2019 13:32:42 -0500 > Segher Boessenkool wrote: > > That is not a fix, that is sweeping the problem under the rug. > > > > As a somewhat dirty hack I added > > > > #if __MSP430X_LARGE__ > > #undef __SIZE_TYPE__ >