public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
* [Bug target/95842] New: arch_names_table and processor_alias_table should be combined
@ 2020-06-23 14:07 hjl.tools at gmail dot com
  2020-06-23 14:22 ` [Bug target/95842] " rguenth at gcc dot gnu.org
                   ` (4 more replies)
  0 siblings, 5 replies; 6+ messages in thread
From: hjl.tools at gmail dot com @ 2020-06-23 14:07 UTC (permalink / raw)
  To: gcc-bugs

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=95842

            Bug ID: 95842
           Summary: arch_names_table and processor_alias_table should be
                    combined
           Product: gcc
           Version: 11.0
            Status: UNCONFIRMED
          Severity: normal
          Priority: P3
         Component: target
          Assignee: unassigned at gcc dot gnu.org
          Reporter: hjl.tools at gmail dot com
                CC: hubicka at ucw dot cz, ubizjak at gmail dot com
  Target Milestone: ---
            Target: i386,x86-64

i386-builtins.c has arch_names_table to map architecture name to internal
model and a switch statement to map internal processor name to architecture
name.  When a new processor name is added, we need to update 3 different
places.  We should put all these information in processor_alias_table.  We
can update a single place in processor_alias_table to support a new processor.

^ permalink raw reply	[flat|nested] 6+ messages in thread

end of thread, other threads:[~2021-03-31  9:57 UTC | newest]

Thread overview: 6+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2020-06-23 14:07 [Bug target/95842] New: arch_names_table and processor_alias_table should be combined hjl.tools at gmail dot com
2020-06-23 14:22 ` [Bug target/95842] " rguenth at gcc dot gnu.org
2020-06-23 22:25 ` hjl.tools at gmail dot com
2020-06-24 11:20 ` cvs-commit at gcc dot gnu.org
2020-06-24 11:26 ` hjl.tools at gmail dot com
2021-03-31  9:57 ` cvs-commit at gcc dot gnu.org

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).