Hvala vam što ste nas kontaktirali.

2018-07-28 Thread Upoznavanje.net
Primili smo vašu poruku i odgovorićemo što pre. Prijatan dan Puno poljubaca, Adminka http://upoznavanje.net";>Upoznavanje.net -- Our mailing address is: upoznavanje.net Durmitorska 15. Sremska mitrovica 22000 Serbia This e

Re: "fall-through" errors

2018-07-28 Thread Eric Gallager
On 7/28/18, Bruce Korb wrote: > ../../autoopts/makeshell.c: In function ‘text_to_var’: > ../../autoopts/makeshell.c:324:14: error: this statement may fall > through [-Werror=implicit-fallthrough=] > (*(opts->pUsageProc))(opts, EXIT_SUCCESS); > ~^~~

Re: "fall-through" errors

2018-07-28 Thread Bruce Korb
On Sat, Jul 28, 2018 at 11:48 AM Jakub Jelinek wrote: > You don't need to use configure for this, something like: > #ifdef __has_attribute > #if __has_attribute(__noreturn__) > #define NORETURN __attribute__((__noreturn__)) > #endif OK. Thanks. It _will_ be a bit more complicated because my

Re: "fall-through" errors

2018-07-28 Thread Jakub Jelinek
On Sat, Jul 28, 2018 at 10:56:24AM -0700, Bruce Korb wrote: > > NOTREACHED means something different, and I don't think we want to add > > support for this when we already support a way (including a standard way) to > > mark function pointers noreturn (noreturn attribute, _Noreturn in C). > > Or yo

Re: "fall-through" errors

2018-07-28 Thread Bruce Korb
On Sat, Jul 28, 2018 at 10:44 AM Jakub Jelinek wrote: > > On Sat, Jul 28, 2018 at 10:22:35AM -0700, Bruce Korb wrote: > > ../../autoopts/makeshell.c: In function ‘text_to_var’: > > ../../autoopts/makeshell.c:324:14: error: this statement may fall > > through [-Werror=implicit-fallthrough=] > >

Re: "fall-through" errors

2018-07-28 Thread Jakub Jelinek
On Sat, Jul 28, 2018 at 10:22:35AM -0700, Bruce Korb wrote: > ../../autoopts/makeshell.c: In function ‘text_to_var’: > ../../autoopts/makeshell.c:324:14: error: this statement may fall > through [-Werror=implicit-fallthrough=] > (*(opts->pUsageProc))(opts, EXIT_SUCCESS); >

"fall-through" errors

2018-07-28 Thread Bruce Korb
../../autoopts/makeshell.c: In function ‘text_to_var’: ../../autoopts/makeshell.c:324:14: error: this statement may fall through [-Werror=implicit-fallthrough=] (*(opts->pUsageProc))(opts, EXIT_SUCCESS); ~^~~~ This warning goes away if

Re: [RFC] Adding Python as a possible language and it's usage

2018-07-28 Thread David Malcolm
On Sat, 2018-07-28 at 10:55 +0100, Ramana Radhakrishnan wrote: > On Fri, Jul 27, 2018 at 3:38 PM, Joseph Myers m> wrote: > > On Fri, 27 Jul 2018, Michael Matz wrote: > > > > > Using any python scripts as part of generally building GCC (i.e. > > > where the > > > generated files aren't prepackaged

Re: Dynamically allocated array of function pointers

2018-07-28 Thread Jonathan Wakely
Please don't cross-post to this list and to gcc-help, this question is off-topic here On Sat, 28 Jul 2018 at 04:01, Vladimir Reshetnikov wrote: > > I'm trying to understand why gcc rejects the dynamic array allocation in > the initializer of e (introducing an alias or additional parenthesization

Re: [RFC] Adding Python as a possible language and it's usage

2018-07-28 Thread Ramana Radhakrishnan
On Fri, Jul 27, 2018 at 3:38 PM, Joseph Myers wrote: > On Fri, 27 Jul 2018, Michael Matz wrote: > >> Using any python scripts as part of generally building GCC (i.e. where the >> generated files aren't prepackaged) will introduce a python dependency for >> distro packages. And for those distros t