public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "schlie at comcast dot net" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug target/20288] AVR assignment of a value through a 16 bit pointer generates out of order code
Date: Fri, 04 Mar 2005 15:26:00 -0000	[thread overview]
Message-ID: <20050304152644.17390.qmail@sourceware.org> (raw)
In-Reply-To: <20050302181643.20288.bob.paddock@gmail.com>


------- Additional Comments From schlie at comcast dot net  2005-03-04 15:26 -------
(In reply to comment #12)
> Everybody who works on the AVR toolchain knows that it would be desirable to
> have attributes to allow objects to be put in and accessed in different address
> spaces. This has nothing to do with this bug report. Who are you trying to
> convince? Please refrain from muddying the waters with comments that have
> nothing to do with the issue at hand. You're just wasting bandwith.

(Although I know I should simply ignore ignorant comments, I feel compelled
to respond.  I pre-apologize, and will not continue the response further than):

Eric, I'm glad it's obvious to you; maybe you'd consider attempting to technically
contribute to the refinement of AVR's GCC port; as opposed to feeling overly
empowered playing secretary for the WINAVR product in which you've obviously
never technically contributed to the refinement of the GCC port which it's based
upon, but instead apparently feel compelled to exert influence over what appears
to obviously be beyond your intimate familiarity, and likely skill set to productively
technically contribute towards yourself.

(Admittedly I am no GCC expert by any stretch of imagination, but observe that
 in my relatively short tenure attempting to familiarize myself with both GCC's
 architecture and the AVR port sufficiently to productively contribute to their
 refinement, I've likely already contributed more (which isn't saying much) than
 you would appear to ever likely accomplish; so please try to tone down your
 misplaced opinions on subjects and people  you're clearly predominantly
 ignorant of.)



-- 


http://gcc.gnu.org/bugzilla/show_bug.cgi?id=20288


  parent reply	other threads:[~2005-03-04 15:26 UTC|newest]

Thread overview: 23+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-03-02 18:17 [Bug c/20288] New: " bob dot paddock at gmail dot com
2005-03-02 18:19 ` [Bug c/20288] " ericw at evcohs dot com
2005-03-02 18:20 ` ericw at evcohs dot com
2005-03-02 18:21 ` [Bug target/20288] " pinskia at gcc dot gnu dot org
2005-03-02 21:24 ` giovannibajo at libero dot it
2005-03-02 22:01 ` ericw at evcohs dot com
2005-03-02 23:07 ` schlie at comcast dot net
2005-03-03 13:13 ` bob dot paddock at gmail dot com
2005-03-03 19:47 ` schlie at comcast dot net
2005-03-03 19:50 ` ericw at evcohs dot com
2005-03-03 22:21 ` bjoern dot m dot haase at web dot de
2005-03-03 22:49 ` j dot gnu at uriah dot heep dot sax dot de
2005-03-03 23:02 ` giovannibajo at libero dot it
2005-03-04 14:14 ` schlie at comcast dot net
2005-03-04 14:19 ` ericw at evcohs dot com
2005-03-04 15:26 ` schlie at comcast dot net [this message]
2005-03-04 19:38 ` bjoern dot m dot haase at web dot de
2005-03-04 19:42 ` bjoern dot m dot haase at web dot de
2005-03-06 21:50 ` cvs-commit at gcc dot gnu dot org
2005-03-06 23:56 ` pinskia at gcc dot gnu dot org
2005-03-13 21:47 ` cvs-commit at gcc dot gnu dot org
2005-03-13 21:49 ` cvs-commit at gcc dot gnu dot org
2005-03-13 22:03 ` pinskia at gcc dot gnu dot 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=20050304152644.17390.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: 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).