Re: about "rename"

2024-06-13 Thread naoki ueda via Gcc-bugs
Ok, thanks. 2024年6月14日(金) 7:51 Andrew Pinski : > On Thu, Jun 13, 2024 at 3:43 PM naoki ueda via Gcc-bugs > wrote: > > > > Although "rename" is not a reserved word, there would be a name conflict > if > > you used it as a function name. > > The rename

about "remove"

2024-06-13 Thread naoki ueda via Gcc-bugs
Although "remove" is not a reserved word, there would be a name conflict if you used it as a function name.

about "rename"

2024-06-13 Thread naoki ueda via Gcc-bugs
Although "rename" is not a reserved word, there would be a name conflict if you used it as a function name.

Re: ’ ] ' is displayed.

2023-12-24 Thread naoki ueda via Gcc-bugs
Thanks for the tip! 2023年12月24日(日) 23:35 Jonathan Wakely : > This mailing list is for automated emails from our bug database, not > for reporting bugs directly. > > See https://gcc.gnu.org/bugs/ for how to report bugs, thanks. > > >

' ] ' is displayed.

2023-12-23 Thread naoki ueda via Gcc-bugs
/* sprintf()関数 */ #include int main(void) { char buffer[80]; double x = 1234.5, y = 678.9, z = -753.1, a = x * y + z; int output_len = sprintf(buffer, "For the input values %f, %f, and %f," "\nthe result was %f.\n", x , y, z, a); puts(buffer); /* if (output_len >= 80) { fprintf(stderr, "Output s

' ] ' is displayed.

2023-12-23 Thread naoki ueda via Gcc-bugs
#include int main(void) { char buffer[80]; double x = 1234.5, y = 678.9, z = -753.1, a = x * y + z; int output_len = sprintf(buffer, "For the input values %f, %f, and %f," "\nthe result was %f.\n", x , y, z, a); puts(buffer);

’ ] ' is displayed.

2023-12-23 Thread naoki ueda via Gcc-bugs
#include int main(void) { char buffer[80]; double x = 1234.5, y = 678.9, z = -753.1, a = x * y + z; int output_len = sprintf(buffer, "For the input values %f, %f, and %f," "\nthe result was %f.\n", x , y, z, a); puts(buffer);

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 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 > > i

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 = 100;

Re: About ' * ' not recognized

2023-01-20 Thread naoki ueda via Gcc-bugs
Ok, I see. 2023年1月21日(土) 10:12 Andrew Pinski : > On Fri, Jan 20, 2023 at 5:05 PM naoki ueda via Gcc-bugs > wrote: > > > > When I tried to execute the attached file mycalc.c with a command line > > argument, it could not be executed normally only in the case of '*&

About ' * ' not recognized

2023-01-20 Thread naoki ueda via Gcc-bugs
When I tried to execute the attached file mycalc.c with a command line argument, it could not be executed normally only in the case of '*'. '+', '-' and '/' can be executed normally, but the compiler cannot execute '*' normally. Isn't this a gcc bug? ~/Clearning$ ./mycalc 20 * 30 用法:mycalc 数値1 演算