LOGIN   :::   RECOVER PASS   :::   GET ACCOUNT    
Browse
  • Projects
  • Code (CVS)
  • Forums
  • News
  • Articles
  • Polls
  •  
    OpenCores
  • FAQ
  • CVS HowTo
  • Mission
  • Media
  • Tools
  • Advertise
  • Mirrors
  • Logos
  • Contact us
  • Job Opportunity
  •  
    Tools
  • Search
      
  • Download Cores (CVSGet)
  •  
    More
  • Wishbone
  • Perlilog
  • EDA tools
  • OpenTech CD
  •  
    Navigation: All forums > Cvs-checkins > Message List > Message Post

    Message

    Reply | Reply all
    Date Prev | Date Next | Thread Prev | Thread Next Date Index | Thread Index

    From: OpenCores CVS Agent <cvs@w...>
    Date: Wed, 9 Apr 2003 19:43:48 -0100
    Subject: [cvs-checkins] or1k/gdb-5.0/gdb or1k-tdep.c
    Top

    CVSROOT:	/home/oc/cvs
    Module name:	or1k
    Changes by:	sfurman	03/04/09 19:43:48
    
    Modified files:
    	gdb-5.0/gdb    : or1k-tdep.c 
    
    Log message:
    	Speed up gdb when running with serial targets:
    	
    	When generating backtraces, the prologue of each function is scanned
    	at least three times by architecture-independent code, e.g. to
    	determine offsets of saved registers, identify frameless functions,
    	etc.  This new code adds straightforward caching of the information
    	gleaned by or1k_scan_prologue() on a per-frame basis rather than
    	storing it in global static variables.  (This benefits both JTAG and
    	serial gdb targets, though the JTAG target runs fast enough that it is
    	not particularly needed.)
    	
    	When the register set is dumped by the serial target, e.g. at any
    	breakpoint or interrupt, the 32 vector/FP registers were included in
    	the dump (each 8 bytes long), though they aren't implemented.  The new
    	code tells gdb that unimplemented registers have zero length in the
    	dump.
    
    
    
    
     
    Copyright (c) 1999 OPENCORES.ORG. All rights reserved.