public inbox for gcc-prs@sourceware.org
help / color / mirror / Atom feed
From: amodra@gcc.gnu.org
To: nobody@gcc.gnu.org
Cc: gcc-prs@gcc.gnu.org,
Subject: target/6413
Date: Tue, 23 Apr 2002 01:16:00 -0000	[thread overview]
Message-ID: <20020423081604.14774.qmail@sources.redhat.com> (raw)

The following reply was made to PR target/6413; it has been noted by GNATS.

From: amodra@gcc.gnu.org
To: gcc-gnats@gcc.gnu.org
Cc:  
Subject: target/6413
Date: 23 Apr 2002 08:11:27 -0000

 CVSROOT:	/cvs/gcc
 Module name:	gcc
 Branch: 	gcc-3_1-branch
 Changes by:	amodra@gcc.gnu.org	2002-04-23 01:11:27
 
 Modified files:
 	gcc            : ChangeLog final.c function.c function.h 
 	                 output.h 
 	gcc/config/i386: i386.c 
 	gcc/config/pa  : pa.c pa.h 
 
 Log message:
 	PR target/6413
 	* function.h: (struct function): Add profile_label_no field.
 	(current_function_profile_label_no): Define.
 	* function.c: (profile_label_no): New static var.
 	(expand_function_start): Increment it, and copy to
 	current_function_profile_label_no.
 	* output.h (profile_label_no): Delete.
 	* final.c (profile_label_no): Delete.
 	(profile_function): Use current_function_profile_label_no.
 	(final_end_function): Don't increment profile_label_no here.
 	* config/i386/i386.c (ix86_osf_output_function_prologue): Replace
 	profile_label_no with current_function_profile_label_no.
 	* config/pa/pa.c (current_function_number): Delete.
 	(pa_output_function_prologue): Don't output profile label here.
 	(hppa_profile_hook): Use label_no param rather than
 	current_function_number.
 	(FUNC_BEGIN_PROLOG_LABEL): Move to ..
 	* config/pa/pa.h: .. here.
 	(FUNCTION_PROFILER): Output profile label here.
 
 Patches:
 http://gcc.gnu.org/cgi-bin/cvsweb.cgi/gcc/gcc/ChangeLog.diff?cvsroot=gcc&only_with_tag=gcc-3_1-branch&r1=1.13152.2.434&r2=1.13152.2.435
 http://gcc.gnu.org/cgi-bin/cvsweb.cgi/gcc/gcc/final.c.diff?cvsroot=gcc&only_with_tag=gcc-3_1-branch&r1=1.241.2.2&r2=1.241.2.3
 http://gcc.gnu.org/cgi-bin/cvsweb.cgi/gcc/gcc/function.c.diff?cvsroot=gcc&only_with_tag=gcc-3_1-branch&r1=1.347.2.8&r2=1.347.2.9
 http://gcc.gnu.org/cgi-bin/cvsweb.cgi/gcc/gcc/function.h.diff?cvsroot=gcc&only_with_tag=gcc-3_1-branch&r1=1.75&r2=1.75.6.1
 http://gcc.gnu.org/cgi-bin/cvsweb.cgi/gcc/gcc/output.h.diff?cvsroot=gcc&only_with_tag=gcc-3_1-branch&r1=1.94&r2=1.94.2.1
 http://gcc.gnu.org/cgi-bin/cvsweb.cgi/gcc/gcc/config/i386/i386.c.diff?cvsroot=gcc&only_with_tag=gcc-3_1-branch&r1=1.368.2.8&r2=1.368.2.9
 http://gcc.gnu.org/cgi-bin/cvsweb.cgi/gcc/gcc/config/pa/pa.c.diff?cvsroot=gcc&only_with_tag=gcc-3_1-branch&r1=1.148.2.3&r2=1.148.2.4
 http://gcc.gnu.org/cgi-bin/cvsweb.cgi/gcc/gcc/config/pa/pa.h.diff?cvsroot=gcc&only_with_tag=gcc-3_1-branch&r1=1.138.2.2&r2=1.138.2.3
 


             reply	other threads:[~2002-04-23  8:16 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-04-23  1:16 amodra [this message]
  -- strict thread matches above, loose matches on Subject: below --
2002-04-23  0:26 target/6413 amodra

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=20020423081604.14774.qmail@sources.redhat.com \
    --to=amodra@gcc.gnu.org \
    --cc=gcc-prs@gcc.gnu.org \
    --cc=nobody@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).