Re: About initialization of automatic variables

2023-04-18 Thread naoki ueda via Gcc-bugs
Ok, I see. 2023年4月18日(火) 17:27 Jonathan Wakely : > The gcc-bugs@gcc.gnu.org list is for automated email from our Bugzilla > database, please don't use it to report bugs or to ask questions about > how GCC works. > > For questions about using GCC send email to gcc-h...@gcc.gnu.org and > to report

Re: About initialization of automatic variables

2023-04-18 Thread Jonathan Wakely via Gcc-bugs
The gcc-bugs@gcc.gnu.org list is for automated email from our Bugzilla database, please don't use it to report bugs or to ask questions about how GCC works. For questions about using GCC send email to gcc-h...@gcc.gnu.org and to report bugs please use bugzilla: https://gcc.gnu.org/bugs/ Thanks!

Re: About initialization of automatic variables

2023-04-18 Thread naoki ueda via Gcc-bugs
Ok, thanks! 2023年4月18日(火) 16:06 Andreas Schwab : > On Apr 18 2023, naoki ueda via Gcc-bugs wrote: > > > The attached code says "int a = 100;", but it should normally be > > initialized with an "undefined value", but in the case of gcc-10, it is > > initialized with "0". Isn't this a bug in

Re: About initialization of automatic variables

2023-04-18 Thread Andreas Schwab
On Apr 18 2023, naoki ueda via Gcc-bugs wrote: > The attached code says "int a = 100;", but it should normally be > initialized with an "undefined value", but in the case of gcc-10, it is > initialized with "0". Isn't this a bug in gcc-10? 0 is just one instance of "undefined value". --

About initialization of automatic variables

2023-04-17 Thread naoki ueda via Gcc-bugs
The attached code says "int a = 100;", but it should normally be initialized with an "undefined value", but in the case of gcc-10, it is initialized with "0". Isn't this a bug in gcc-10? #include int main(void) { int n; for (n = 1;n <= 5;n++) { switch (n) { int a =