From: Andrew Cagney <cagney@gnu.org>
To: Orjan Friberg <orjan.friberg@axis.com>
Cc: gdb-patches@sources.redhat.com
Subject: Re: New port: CRISv32
Date: Fri, 14 Jan 2005 17:42:00 -0000 [thread overview]
Message-ID: <41E803F5.2020307@gnu.org> (raw)
In-Reply-To: <41E79606.40302@axis.com>
Orjan Friberg wrote:
> Well, here it is. The oft-talked-about, but never-yet-submitted one.
> Since I am a CRIS maintainer and this only touches CRIS-specific files I
> assume I'm free to check this in, but in case anything is questionable
> (such as resurrecting the tm-cris.h file) and/or plain out wrong, here
> it is.
>
> Oh, some recent gdb.base testsuite results:
>
> # of expected passes 6240
> # of unexpected failures 39
> # of expected failures 6
> # of known failures 5
> # of unresolved testcases 1
> # of untested testcases 1
> # of unsupported tests 12
>
>
> 2005-01-15 Orjan Friberg <orjanf@axis.com>
>
> * config/cris/tm-cris.h: Resurrect.
> (TARGET_HAS_HARDWARE_WATCHPOINTS, TARGET_CAN_USE_HARDWARE_WATCHPOINT)
> (TARGET_REGION_OK_FOR_HW_WATCHPOINT): Define.
Yep, bear trap.
You'll see that MarkK's being elimiating the TM files and the TM_FILE
macro is now deprecated (and you can't add deprecated stuff :-)
We're going to need to figure out how to fix things so that these macros
are avoided.
Andrew
next prev parent reply other threads:[~2005-01-14 17:42 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-01-14 9:51 Orjan Friberg
2005-01-14 17:42 ` Andrew Cagney [this message]
2005-01-25 14:40 ` Orjan Friberg
2005-01-25 14:45 ` Orjan Friberg
2005-01-25 14:48 ` Daniel Jacobowitz
2005-01-25 15:03 ` Orjan Friberg
2005-01-25 15:06 ` Daniel Jacobowitz
2005-01-25 16:23 ` Orjan Friberg
2005-01-25 17:03 ` Daniel Jacobowitz
2005-01-25 16:08 ` Andrew Cagney
2005-01-25 16:28 ` Orjan Friberg
2005-01-25 16:39 ` Andrew Cagney
2005-01-26 12:36 ` Orjan Friberg
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=41E803F5.2020307@gnu.org \
--to=cagney@gnu.org \
--cc=gdb-patches@sources.redhat.com \
--cc=orjan.friberg@axis.com \
/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