public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "gjl at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug target/63223] [avr] Make jumptables work with -Wl,--section-start,.text=
Date: Tue, 21 Oct 2014 09:38:00 -0000	[thread overview]
Message-ID: <bug-63223-4-7in5hFI0JQ@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-63223-4@http.gcc.gnu.org/bugzilla/>

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=63223

--- Comment #8 from Georg-Johann Lay <gjl at gcc dot gnu.org> ---
(In reply to Jorn Wolfgang Rennecke from comment #4)
> (In reply to Georg-Johann Lay from comment #1)
> do_global_dtors is supposed to start at the start and increment from there.
> I see it used to be half-way wrong and half-way correct.
> (Starting at the start, decrementing for __AVR_HAVE_ELPM__, incrementing
> otherwise.)
> However, you now made it all the way use an incorrect order - starting at the
> end and incrementing from there.
> Is there a rationale for this?

The old code was broken as it decremented begainning at the start address.  The
flaw never came apparent for __dtors_start = __dtors_end or with simulators
that terminated in exit.

The new code uses the same traverse direction like __do_global_ctors.

Is the order of .ctors, .dtors defined in any way?  I.e. how do you express
that constructor A must run before constructor B in the C program?  Same for
destructors.


  parent reply	other threads:[~2014-10-21  9:31 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-09-11  7:56 [Bug target/63223] New: " gjl at gcc dot gnu.org
2014-09-11  8:09 ` [Bug target/63223] " gjl at gcc dot gnu.org
2014-09-11  8:20 ` gjl at gcc dot gnu.org
2014-09-11  8:22 ` gjl at gcc dot gnu.org
2014-10-17 14:40 ` amylaar at gcc dot gnu.org
2014-10-17 14:56 ` amylaar at gcc dot gnu.org
2014-10-17 15:11 ` amylaar at gcc dot gnu.org
2014-10-17 15:47 ` amylaar at gcc dot gnu.org
2014-10-21  9:38 ` gjl at gcc dot gnu.org [this message]
2014-10-21 14:13 ` amylaar at gcc dot gnu.org
2014-10-21 16:12 ` amylaar at gcc dot gnu.org
2014-10-22  8:51 ` gjl at gcc dot gnu.org
2014-10-22 12:02 ` gjl 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-63223-4-7in5hFI0JQ@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).