Talk:Compiler/Archive 4: Difference between revisions

From Citizendium
Jump to navigation Jump to search
imported>Pat Palmer
(more about my concerns)
imported>Pat Palmer
(delete this list as duplicating what's now in compilers?)
Line 12: Line 12:


__TOC__
__TOC__
=first impression=
At quick first glance (it's very late by now), I'm not sure I agree that all these things should be on the list.  They are certainly topics within [[computer architecture]].  We can work it out later, but I hope no one is terribly attached to this particular list in its current incarnation.  It's good to have placeholders, though.[[User:Pat Palmer|Pat Palmer]] 04:08, 9 May 2007 (CDT)
At quick first glance (it's very late by now), I'm not sure I agree that all these things should be on the list.  They are certainly topics within [[computer architecture]].  We can work it out later, but I hope no one is terribly attached to this particular list in its current incarnation.  It's good to have placeholders, though.[[User:Pat Palmer|Pat Palmer]] 04:08, 9 May 2007 (CDT)


::Mainly, I'm concerned that we have some things on the list that really have to do with how the processor optimizes execution at runtime to make itself seem to go faster.  Things like "static scheduling" are indeed done by compilers, but a things like register renaming are done by the processor hardware (which admittedly is doing compiler-like things).[[User:Pat Palmer|Pat Palmer]] 04:10, 9 May 2007 (CDT)
::Mainly, I'm concerned that we have some things on the list that really have to do with how the processor optimizes execution at runtime to make itself seem to go faster.  Things like "static scheduling" are indeed done by compilers, but a things like register renaming are done by the processor hardware (which admittedly is doing compiler-like things).[[User:Pat Palmer|Pat Palmer]] 04:10, 9 May 2007 (CDT)
=second impression=
I have copied the entire list into [[compiler]], so I'm not sure it's helpful to keep this as a separate list.  It's generally a bad idea to duplicate information, and this stuff possibly needs to be introduced and summarized on the compiler page, in which case, maybe we should delete this extra copy of them.

Revision as of 04:13, 9 May 2007


Article Checklist for "Compiler/Archive 4"
Workgroup category or categories Computers Workgroup [Editors asked to check categories]
Article status Stub: no more than a few sentences
Underlinked article? Yes
Basic cleanup done? No
Checklist last edited by --Nick Johnson 15:15, 11 April 2007 (CDT)

To learn how to fill out this checklist, please see CZ:The Article Checklist.





first impression

At quick first glance (it's very late by now), I'm not sure I agree that all these things should be on the list. They are certainly topics within computer architecture. We can work it out later, but I hope no one is terribly attached to this particular list in its current incarnation. It's good to have placeholders, though.Pat Palmer 04:08, 9 May 2007 (CDT)

Mainly, I'm concerned that we have some things on the list that really have to do with how the processor optimizes execution at runtime to make itself seem to go faster. Things like "static scheduling" are indeed done by compilers, but a things like register renaming are done by the processor hardware (which admittedly is doing compiler-like things).Pat Palmer 04:10, 9 May 2007 (CDT)

second impression

I have copied the entire list into compiler, so I'm not sure it's helpful to keep this as a separate list. It's generally a bad idea to duplicate information, and this stuff possibly needs to be introduced and summarized on the compiler page, in which case, maybe we should delete this extra copy of them.