From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 15303 invoked by alias); 30 Oct 2011 08:38:26 -0000 Received: (qmail 15288 invoked by uid 22791); 30 Oct 2011 08:38:25 -0000 X-SWARE-Spam-Status: No, hits=-3.0 required=5.0 tests=AWL,BAYES_00,DKIM_SIGNED,DKIM_VALID,RCVD_IN_DNSWL_LOW,RP_MATCHES_RCVD,TW_NW X-Spam-Check-By: sourceware.org Received: from csmailer.cs.nctu.edu.tw (HELO csmailer.cs.nctu.edu.tw) (140.113.235.130) by sourceware.org (qpsmtpd/0.43rc1) with ESMTP; Sun, 30 Oct 2011 08:38:05 +0000 Received: from csmailer.cs.nctu.edu.tw (localhost [127.0.0.1]) by csmailer.cs.nctu.edu.tw (Postfix) with ESMTP id 850CFA33; Sun, 30 Oct 2011 16:36:23 +0800 (CST) Received: from alumni.cs.nctu.edu.tw (alumni.cs.nctu.edu.tw [140.113.235.116]) by csmailer.cs.nctu.edu.tw (Postfix) with ESMTP id 63B6AA32; Sun, 30 Oct 2011 16:36:23 +0800 (CST) Received: (from chenwj@localhost) by alumni.cs.nctu.edu.tw (8.14.4/8.14.4/Submit) id p9U8c3f9046648; Sun, 30 Oct 2011 16:38:03 +0800 (CST) (envelope-from chenwj) Date: Sun, 30 Oct 2011 08:38:00 -0000 From: =?utf-8?B?6Zmz6Z+L5Lu7?= To: asmwarrior Cc: gcc-help@gcc.gnu.org, "gcc@gcc.gnu.org" Subject: Re: Why running the next command will jump back to the previous line position Message-ID: <20111030083803.GA43643@cs.nctu.edu.tw> References: <4EABA71D.600@gmail.com> <4EABB25B.40208@gmail.com> <4EAC0B83.2010003@gmail.com> MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Disposition: inline In-Reply-To: <4EAC0B83.2010003@gmail.com> User-Agent: Mutt/1.5.21 (2010-09-15) Content-Transfer-Encoding: quoted-printable X-IsSubscribed: yes Mailing-List: contact gcc-help-help@gcc.gnu.org; run by ezmlm Precedence: bulk List-Id: List-Archive: List-Post: List-Help: Sender: gcc-help-owner@gcc.gnu.org X-SW-Source: 2011-10/txt/msg00247.txt.bz2 > Hi, all. It looks like some one has report a similar bug on: >=20 > http://gcc.gnu.org/bugzilla/show_bug.cgi?id=3D49951 >=20 > and it has caused by the revision: >=20 > http://gcc.gnu.org/viewcvs?root=3Dgcc&view=3Drev&rev=3D149722 >=20 > Any GCC developer can have look at it? Maybe you can ask GCC C++ frontend developers (see ${SOURCE}/MAINTAINERS) directly. Perhaps they can tell you where to start to fix the problem. :-) Regards, chenwj --=20 Wei-Ren Chen (=E9=99=B3=E9=9F=8B=E4=BB=BB) Computer Systems Lab, Institute of Information Science, Academia Sinica, Taiwan (R.O.C.) Tel:886-2-2788-3799 #1667