public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "alexey at hyperroll dot com" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug c/24542] potential integer overflow should be warned on assignment to wider variable Date: Wed, 26 Oct 2005 17:12:00 -0000 [thread overview] Message-ID: <20051026171250.29282.qmail@sourceware.org> (raw) In-Reply-To: <bug-24542-11594@http.gcc.gnu.org/bugzilla/> ------- Comment #5 from alexey at hyperroll dot com 2005-10-26 17:12 ------- Sir, it's my first report here, and I see the code first time. I hope that both comments #3 and #4 are not for me. Or am I mistaken? Otherwise, what document (preferably, short) should I read to understand the ideology of the parse tree, and its details. Also, why have I done the parser non-bison compatible? I've taken the stable release, not the CVS revision. -- http://gcc.gnu.org/bugzilla/show_bug.cgi?id=24542
next prev parent reply other threads:[~2005-10-26 17:12 UTC|newest] Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top 2005-10-26 14:54 [Bug c/24542] New: " alexey at hyperroll dot com 2005-10-26 15:01 ` [Bug c/24542] " alexey at hyperroll dot com 2005-10-26 15:03 ` alexey at hyperroll dot com 2005-10-26 15:59 ` [Bug c/24542] potential " pinskia at gcc dot gnu dot org 2005-10-26 16:00 ` pinskia at gcc dot gnu dot org 2005-10-26 17:12 ` alexey at hyperroll dot com [this message] 2005-11-01 22:29 ` pinskia at gcc dot gnu dot org 2006-03-13 21:49 ` alexey at hyperroll dot com 2006-03-13 21:52 ` pinskia at gcc dot gnu dot org 2006-09-18 0:18 ` pinskia at gcc dot gnu dot org 2006-09-18 5:48 ` alexey at hyperroll dot com [not found] <bug-24542-4@http.gcc.gnu.org/bugzilla/> 2023-03-31 7:16 ` pinskia at gcc dot gnu.org 2023-03-31 8:15 ` zhangboyang.id at gmail dot com
Reply instructions: You may reply publicly to this message via plain-text email using any one of the following methods: * Save the following mbox file, import it into your mail client, and reply-to-all from there: mbox Avoid top-posting and favor interleaved quoting: https://en.wikipedia.org/wiki/Posting_style#Interleaved_style * Reply using the --to, --cc, and --in-reply-to switches of git-send-email(1): git send-email \ --in-reply-to=20051026171250.29282.qmail@sourceware.org \ --to=gcc-bugzilla@gcc.gnu.org \ --cc=gcc-bugs@gcc.gnu.org \ /path/to/YOUR_REPLY https://kernel.org/pub/software/scm/git/docs/git-send-email.html * If your mail client supports setting the In-Reply-To header via mailto: links, try the mailto: linkBe sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions for how to clone and mirror all data and code used for this inbox; as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).