public inbox for gdb-testers@sourceware.org help / color / mirror / Atom feed
From: gdb-buildbot@sergiodj.net To: gdb-testers@sourceware.org Subject: [binutils-gdb] gdb/djgpp: Add Hygon Dhyana processor support Date: Wed, 21 Aug 2019 18:41:00 -0000 [thread overview] Message-ID: <3960cb7a1bf14016b6b16d35205cdcb9dfc43c27@gdb-build> (raw) *** TEST RESULTS FOR COMMIT 3960cb7a1bf14016b6b16d35205cdcb9dfc43c27 *** commit 3960cb7a1bf14016b6b16d35205cdcb9dfc43c27 Author: Jinke Fan <fanjinke51@yeah.net> AuthorDate: Wed May 15 17:34:57 2019 +0800 Commit: Pedro Alves <palves@redhat.com> CommitDate: Wed Aug 21 18:07:39 2019 +0100 gdb/djgpp: Add Hygon Dhyana processor support Chengdu Haiguang IC Design Co., Ltd (Hygon) is a Joint Venture between AMD and Haiguang Information Technology Co.,Ltd., which aims at providing high performance x86 processors for the China server market. Its first generation processor codename is Dhyana, which originates from AMD technology and shares most of the architecture with AMD's family 17h, but with different CPU Vendor ID("HygonGenuine")/Family series number(Family 18h). gdb/ChangeLog: 2019-08-21 Jinke Fan <fanjinke51@yeah.net> * go32-nat.c (go32_sysinfo): Add hygon_p. diff --git a/gdb/ChangeLog b/gdb/ChangeLog index 41d02a6b49..3d9c3ce1b1 100644 --- a/gdb/ChangeLog +++ b/gdb/ChangeLog @@ -1,3 +1,7 @@ +2019-08-21 Jinke Fan <fanjinke51@yeah.net> + + * go32-nat.c (go32_sysinfo): Add hygon_p. + 2019-08-20 Tom Tromey <tom@tromey.com> * tui/tui-regs.h (struct tui_data_window) <last_regs_line_no, diff --git a/gdb/go32-nat.c b/gdb/go32-nat.c index 6a58565fef..81fcfe2c2a 100644 --- a/gdb/go32-nat.c +++ b/gdb/go32-nat.c @@ -1162,6 +1162,7 @@ go32_sysinfo (const char *arg, int from_tty) unsigned brand_idx; int intel_p = strcmp (cpuid_vendor, "GenuineIntel") == 0; int amd_p = strcmp (cpuid_vendor, "AuthenticAMD") == 0; + int hygon_p = strcmp (cpuid_vendor, "HygonGenuine") == 0; unsigned cpu_family, cpu_model; #if 0 @@ -1261,12 +1262,12 @@ go32_sysinfo (const char *arg, int from_tty) } } xsnprintf (cpu_string, sizeof (cpu_string), "%s%s Model %d Stepping %d", - intel_p ? "Pentium" : (amd_p ? "AMD" : "ix86"), + intel_p ? "Pentium" : (amd_p ? "AMD" : (hygon_p ? "Hygon" : "ix86")), cpu_brand, cpu_model, cpuid_eax & 0xf); printfi_filtered (31, "%s\n", cpu_string); if (((cpuid_edx & (6 | (0x0d << 23))) != 0) || ((cpuid_edx & 1) == 0) - || (amd_p && (cpuid_edx & (3 << 30)) != 0)) + || ((amd_p || hygon_p) && (cpuid_edx & (3 << 30)) != 0)) { puts_filtered ("CPU Features..................."); /* We only list features which might be useful in the DPMI @@ -1285,7 +1286,7 @@ go32_sysinfo (const char *arg, int from_tty) puts_filtered ("SSE "); if ((cpuid_edx & (1 << 26)) != 0) puts_filtered ("SSE2 "); - if (amd_p) + if (amd_p || hygon_p) { if ((cpuid_edx & (1 << 31)) != 0) puts_filtered ("3DNow! ");
next reply other threads:[~2019-08-21 18:36 UTC|newest] Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top 2019-08-21 18:41 gdb-buildbot [this message] 2019-08-21 18:44 ` *** COMPILATION FAILED *** Failures on Fedora-x86_64-cc-with-index, branch master *** BREAKAGE *** gdb-buildbot 2019-08-21 18:49 ` *** COMPILATION FAILED *** Failures on Fedora-x86_64-m32, " gdb-buildbot 2019-08-21 18:50 ` *** COMPILATION FAILED *** Failures on Fedora-x86_64-m64, " gdb-buildbot 2019-08-21 18:51 ` Failures on Fedora-i686, branch master gdb-buildbot 2019-08-21 18:53 ` *** COMPILATION FAILED *** Failures on Fedora-x86_64-native-gdbserver-m32, branch master *** BREAKAGE *** gdb-buildbot 2019-08-21 18:54 ` *** COMPILATION FAILED *** Failures on Fedora-x86_64-native-extended-gdbserver-m32, " gdb-buildbot 2019-08-21 20:46 ` *** COMPILATION FAILED *** Failures on Fedora-x86_64-native-extended-gdbserver-m64, " gdb-buildbot 2019-08-21 20:46 ` *** COMPILATION FAILED *** Failures on Fedora-x86_64-native-gdbserver-m64, " gdb-buildbot 2019-08-21 20:51 ` Failures on Ubuntu-Aarch64-native-extended-gdbserver-m64, branch master gdb-buildbot
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=3960cb7a1bf14016b6b16d35205cdcb9dfc43c27@gdb-build \ --to=gdb-buildbot@sergiodj.net \ --cc=gdb-testers@sourceware.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: linkBe 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).