public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "artemeas at gmail dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug target/49764] [gcc-avr] Compiling for Arduino is not working
Date: Sat, 16 Jul 2011 17:57:00 -0000 [thread overview]
Message-ID: <bug-49764-4-X51geV4K6X@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-49764-4@http.gcc.gnu.org/bugzilla/>
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=49764
--- Comment #4 from _artem_ <artemeas at gmail dot com> 2011-07-16 17:57:28 UTC ---
thank YOU master clearness!
I did that before I posted the bug here. PROOF:
https://bugs.archlinux.org/task/25136
Please don't be stupid, OK?
And please do this on your machine:
1. go to arduino.cc
2. download the ide (EVEN IF YOU DON'T HAVE AN ARDUINO BOARD, just download it
TO SEE and TO REALIZE that's a gcc-avr/avr-gcc (call it what you want) bug.
3. start the ide (you even don't need to install it, just extract and run)
4. CLICK ON THE COMPILE ICON (without loading any examples, you don't even need
a line of code to reproduce the bug)
please do this on gcc-avr 4.6.0 and then on gcc-avr 4.6.1 and then again on
gcc-avr-4.6.1 to realize that you're a stupid moron.
Second proof that you're a stupid and INCOMPETENT person: since gcc/gcc-avr
4.5.2 when you compile a arduino code and upload it to the microcontroller
everything goes well, NO ERRORS, but the biggest fail is that on the board ANY
delay() function freezes the board. When you upload the SAME (THE SAME) code
from a windows (OS) machine the delay() function works as expected.
So don't troll that's not a gcc issue, BECAUSE IT IS GCC bug.
p.s. you won't die if you just download and run the above listed program to see
that's a gcc bug and not ide bug. I repeat, everything works except delay()
function on 4.6.0 but not on 4.6.1
next prev parent reply other threads:[~2011-07-16 17:57 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-07-16 16:44 [Bug target/49764] New: " artemeas at gmail dot com
2011-07-16 16:47 ` [Bug target/49764] " artemeas at gmail dot com
2011-07-16 17:26 ` redi at gcc dot gnu.org
2011-07-16 17:34 ` redi at gcc dot gnu.org
2011-07-16 17:57 ` artemeas at gmail dot com [this message]
2011-07-16 18:10 ` redi at gcc dot gnu.org
2011-07-16 18:13 ` redi at gcc dot gnu.org
2011-07-16 19:06 ` artemeas at gmail dot com
2011-07-16 19:36 ` redi at gcc dot gnu.org
2011-07-16 19:55 ` artemeas at gmail dot com
2011-07-16 20:26 ` redi at gcc dot gnu.org
2011-07-17 0:30 ` artemeas at gmail dot com
2011-07-17 9:55 ` redi at gcc dot gnu.org
2011-07-17 9:57 ` redi at gcc dot gnu.org
2011-07-17 10:03 ` redi at gcc dot gnu.org
2011-07-23 18:42 ` gjl at gcc dot gnu.org
2011-07-23 19:27 ` gjl at gcc dot gnu.org
2011-07-23 19:30 ` gjl at gcc dot gnu.org
2011-07-25 10:24 ` [Bug target/49764] [avr-g++] Rejects attribute progmem gjl at gcc dot gnu.org
2011-07-26 19:34 ` artemeas at gmail dot com
2011-07-27 1:19 ` redi at gcc dot gnu.org
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=bug-49764-4-X51geV4K6X@http.gcc.gnu.org/bugzilla/ \
--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: link
Be 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).