|
From: Nicholas N. <nj...@cs...> - 2005-11-12 22:36:55
|
Hi, Is there an easy way to learn when GCC options were introduced? I've found that I can speed up Cachegrind by 6--8% by inlining the cachesim_*_doref() functions. But because they're big, I need to set "--param max-inline-insns-single=2000", which says "inline big functions that are marked 'inline'". So I want to know when this --param option was introduced, to know if I can just use it straight up or if some fiddling is required. Thanks. Nick |
|
From: Greg P. <gp...@us...> - 2005-11-13 02:39:45
|
Nicholas Nethercote writes: > Is there an easy way to learn when GCC options were introduced? > > I've found that I can speed up Cachegrind by 6--8% by inlining the > cachesim_*_doref() functions. But because they're big, I need to set > "--param max-inline-insns-single=2000", which says "inline big functions > that are marked 'inline'". So I want to know when this --param option was > introduced, to know if I can just use it straight up or if some fiddling > is required. gcc's inlining options change frequently. Even if the option is present, its meaning may change. You may have better luck with __attribute__((always_inline)), which dates from gcc 3.1 or so. -- Greg Parker gp...@us... |
|
From: Dirk M. <dm...@gm...> - 2005-11-14 13:47:32
|
On Saturday 12 November 2005 23:36, Nicholas Nethercote wrote: > Is there an easy way to learn when GCC options were introduced? write a configure check that tests if the compiler still compiles if you add a specific command line option. Dirk |