public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "jan dot kratochvil at redhat dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug debug/36748] scev const-prop pass adds bad line numbers
Date: Sat, 06 Dec 2008 13:23:00 -0000	[thread overview]
Message-ID: <20081206132221.18329.qmail@sourceware.org> (raw)
In-Reply-To: <bug-36748-3264@http.gcc.gnu.org/bugzilla/>



------- Comment #2 from jan dot kratochvil at redhat dot com  2008-12-06 13:22 -------
It looks fixed in 4.4 for me, tested on:
GNU C (GCC) version 4.4.0 20081202 (experimental) (x86_64-unknown-linux-gnu)
        compiled by GNU C version 4.4.0 20081202 (experimental), GMP version
4.2.2, MPFR version 2.3.2.
GGC heuristics: --param ggc-min-expand=30 --param ggc-min-heapsize=4096

Line 13 in .line_debug is now assigned only to the "main" address (in Fedora
gcc-4.3.2-7.x86_64 it was assigned also to the "factorial" address).

Expecting it got fixed by Jakub Jelinek as a part of the Bug 36690.


-- 

jan dot kratochvil at redhat dot com changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |jan dot kratochvil at redhat
                   |                            |dot com


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


  parent reply	other threads:[~2008-12-06 13:23 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-07-07 13:48 [Bug debug/36748] New: " drow at gcc dot gnu dot org
2008-07-07 13:57 ` [Bug debug/36748] " drow at gcc dot gnu dot org
2008-12-06 13:23 ` jan dot kratochvil at redhat dot com [this message]
2008-12-06 15:20 ` drow at gcc dot gnu dot org
2008-12-06 15:21 ` drow at gcc dot gnu dot org
     [not found] <bug-36748-4@http.gcc.gnu.org/bugzilla/>
2021-12-20  0:46 ` pinskia 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=20081206132221.18329.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).