> -----Original Message----- > From: Petar Jovanovic [mailto:petar.jovano...@rt-rk.com] > Sent: Thursday, February 12, 2015 7:28 PM > Subject: RE: [PATCH v2][MIPS] fix CRT_CALL_STATIC_FUNCTION macro > > -----Original Message----- > From: Moore, Catherine [mailto:catherine_mo...@mentor.com] > Sent: Friday, February 6, 2015 4:13 PM > To: Matthew Fortune; Petar Jovanovic; gcc-patches@gcc.gnu.org; 'Maciej W. > Rozycki' > Subject: RE: [PATCH v2][MIPS] fix CRT_CALL_STATIC_FUNCTION macro > > > > Petar, would you please add your testcase to the gcc testsuite and repost > the patch. > > Hi Catherine, > > Sure, I can repost the patch and add the test case I used. > My concern - and I would appreciate feedback from you and others on it - is > that the test I originally used to report [1] the problem creates a large > executable (380 MB). > > > The test also takes time to execute. Obviously, I can make it slightly more > complex and make execute time short. Another path is to introduce and use > options such as "Wl,-Ttext-segment" to make its size smaller. Any other > ideas? > Hi Petar,
There isn't any need to execute a large testcase. Instead, try adding a short version of your test to the directory gcc/testsuite/gcc.target/mips. There are examples of other tests there they check for specific assembler sequences by using scan-assembler. See umips-swp-1.c (and others) for a specific example of how to do this. Let me know if you need additional help. Thanks, Catherine
