* Supported Systems page on the Wiki @ 2019-01-25 17:50 John Baldwin 2019-01-25 17:59 ` Pedro Alves 0 siblings, 1 reply; 5+ messages in thread From: John Baldwin @ 2019-01-25 17:50 UTC (permalink / raw) To: Pedro Alves; +Cc: gdb I was looking at the supported systems page on the wiki recently (I made some minor updates yesterday) and noticed the second table (Supported Targets) is currently missing. There also isn't a table for which configurations support native targets. Thinking about this a bit more, I feel that if we do fill in the missing second table the page would probably end up a bit long. If we further added a table listing native targets, that would make the page even longer. So, what would you all think about maybe reworking the page to use a single table and have columns in that table for Target, Host, Native, and GDB Server? We could then use the MoinMoin syntax for checkmarks "(./)" to indicate which of those columns were supported for a given target. We could also add a brief legend at the top of the table defining what we mean by Target, Host, etc. as well. -- John Baldwin                                                                             ^ permalink raw reply [flat|nested] 5+ messages in thread
* Re: Supported Systems page on the Wiki 2019-01-25 17:50 Supported Systems page on the Wiki John Baldwin @ 2019-01-25 17:59 ` Pedro Alves 2019-01-25 19:08 ` John Baldwin 0 siblings, 1 reply; 5+ messages in thread From: Pedro Alves @ 2019-01-25 17:59 UTC (permalink / raw) To: John Baldwin; +Cc: gdb On 01/25/2019 05:48 PM, John Baldwin wrote: > I was looking at the supported systems page on the wiki recently (I made > some minor updates yesterday) and noticed the second table (Supported Targets) > is currently missing. There also isn't a table for which configurations > support native targets. Thinking about this a bit more, I feel that if we > do fill in the missing second table the page would probably end up a bit > long. If we further added a table listing native targets, that would make > the page even longer. I'd think a table listing native targets would be about the same as the hosts table, though. > So, what would you all think about maybe reworking the > page to use a single table and have columns in that table for Target, Host, > Native, and GDB Server? We could then use the MoinMoin syntax for checkmarks > "(./)" to indicate which of those columns were supported for a given target. > We could also add a brief legend at the top of the table defining what we > mean by Target, Host, etc. as well. Sounds good to me in principle. Thanks, Pedro Alves ^ permalink raw reply [flat|nested] 5+ messages in thread
* Re: Supported Systems page on the Wiki 2019-01-25 17:59 ` Pedro Alves @ 2019-01-25 19:08 ` John Baldwin 2019-01-25 20:13 ` Pedro Alves 0 siblings, 1 reply; 5+ messages in thread From: John Baldwin @ 2019-01-25 19:08 UTC (permalink / raw) To: Pedro Alves; +Cc: gdb On 1/25/19 9:59 AM, Pedro Alves wrote: > On 01/25/2019 05:48 PM, John Baldwin wrote: >> I was looking at the supported systems page on the wiki recently (I made >> some minor updates yesterday) and noticed the second table (Supported Targets) >> is currently missing. There also isn't a table for which configurations >> support native targets. Thinking about this a bit more, I feel that if we >> do fill in the missing second table the page would probably end up a bit >> long. If we further added a table listing native targets, that would make >> the page even longer. > > I'd think a table listing native targets would be about the same as the > hosts table, though. That was a question I forgot to ask is does a Native column even make sense or will it effectively always be true that if GDB is supposed as a host and a target it probably has a native target as well? -- John Baldwin                                                                             ^ permalink raw reply [flat|nested] 5+ messages in thread
* Re: Supported Systems page on the Wiki 2019-01-25 19:08 ` John Baldwin @ 2019-01-25 20:13 ` Pedro Alves 2019-01-25 20:39 ` John Baldwin 0 siblings, 1 reply; 5+ messages in thread From: Pedro Alves @ 2019-01-25 20:13 UTC (permalink / raw) To: John Baldwin; +Cc: gdb On 01/25/2019 07:06 PM, John Baldwin wrote: > On 1/25/19 9:59 AM, Pedro Alves wrote: >> On 01/25/2019 05:48 PM, John Baldwin wrote: >>> I was looking at the supported systems page on the wiki recently (I made >>> some minor updates yesterday) and noticed the second table (Supported Targets) >>> is currently missing. There also isn't a table for which configurations >>> support native targets. Thinking about this a bit more, I feel that if we >>> do fill in the missing second table the page would probably end up a bit >>> long. If we further added a table listing native targets, that would make >>> the page even longer. >> >> I'd think a table listing native targets would be about the same as the >> hosts table, though. > > That was a question I forgot to ask is does a Native column even make sense > or will it effectively always be true that if GDB is supposed as a host > and a target it probably has a native target as well? > In the general case, that could well be false. But in practice, I'm not sure the general case matters. I'd assume that any POSIX-like OS supported by gnulib will be able to build gdb, even if we don't have a native port for it, or target support. That GDB would be usable as a cross/remote debugger. Is it useful to try to find such systems and list them in the table with only a "host" column checked? Probably not. Cases that come to mind are native ports for which support was obsoleted and removed, _and_ don't barf on the "Configuration $host is obsolete." check in gdb/configure.host. Speaking of which, I guess pedantically that error is incorrect, since you could pedantically still want to build a cross debugger hosted on those systems... Other cases could be some new new architecture running Linux, *BSD, etc. I'd assume that it is usually possible to build and use GDB as a cross debugger on such a system, even if we don't have a native port yet, because new native ports for new architectures don't usually need fixes to common code. Assuming GDB already supports the operating system, that is, of course. We could look at the set of gdbserver's supported systems and compare that to gdb's native systems. There are a number of ports for which there are no corresponding gdb native support files. CRIS Linux, for example? But those would already get a line in the table, with checks on the "target" and "gdbserver" columns. Is is useful to try to determine whether gdb can be built on such a system, even if it doesn't support native debugging? Doubt it. Maybe just a general "GDB builds on most POSIX-like hosts." remark is sufficient. Then we would only have the "native" column, no "host" column. Of course, we can always change the table if we find a use for adding info. Thanks, Pedro Alves ^ permalink raw reply [flat|nested] 5+ messages in thread
* Re: Supported Systems page on the Wiki 2019-01-25 20:13 ` Pedro Alves @ 2019-01-25 20:39 ` John Baldwin 0 siblings, 0 replies; 5+ messages in thread From: John Baldwin @ 2019-01-25 20:39 UTC (permalink / raw) To: Pedro Alves; +Cc: gdb On 1/25/19 12:12 PM, Pedro Alves wrote: > On 01/25/2019 07:06 PM, John Baldwin wrote: > Maybe just a general "GDB builds on most POSIX-like hosts." remark > is sufficient. Then we would only have the "native" column, no > "host" column. Ok, that sounds reasonable to me. I can take a first stab at this over the next few days unless someone beats me to it. -- John Baldwin                                                                             ^ permalink raw reply [flat|nested] 5+ messages in thread
end of thread, other threads:[~2019-01-25 20:39 UTC | newest] Thread overview: 5+ messages (download: mbox.gz / follow: Atom feed) -- links below jump to the message on this page -- 2019-01-25 17:50 Supported Systems page on the Wiki John Baldwin 2019-01-25 17:59 ` Pedro Alves 2019-01-25 19:08 ` John Baldwin 2019-01-25 20:13 ` Pedro Alves 2019-01-25 20:39 ` John Baldwin
This is a public inbox, see mirroring instructions for how to clone and mirror all data and code used for this inbox