<feed xmlns='http://www.w3.org/2005/Atom'>
<title>bcm5719-llvm/clang/test/CodeGenCXX/default-destructor-nested.cpp, branch meklort-10.0.1</title>
<subtitle>Project Ortega BCM5719 LLVM</subtitle>
<id>https://git.raptorcs.com/git/bcm5719-llvm/atom?h=meklort-10.0.1</id>
<link rel='self' href='https://git.raptorcs.com/git/bcm5719-llvm/atom?h=meklort-10.0.1'/>
<link rel='alternate' type='text/html' href='https://git.raptorcs.com/git/bcm5719-llvm/'/>
<updated>2014-01-14T19:35:09+00:00</updated>
<entry>
<title>Remove the -cxx-abi command-line flag.</title>
<updated>2014-01-14T19:35:09+00:00</updated>
<author>
<name>Hans Wennborg</name>
<email>hans@hanshq.net</email>
</author>
<published>2014-01-14T19:35:09+00:00</published>
<link rel='alternate' type='text/html' href='https://git.raptorcs.com/git/bcm5719-llvm/commit/?id=c9bd88e6811fb622cde644a82eac41c0b02c00ee'/>
<id>urn:sha1:c9bd88e6811fb622cde644a82eac41c0b02c00ee</id>
<content type='text'>
This makes the C++ ABI depend entirely on the target: MS ABI for -win32 triples,
Itanium otherwise. It's no longer possible to do weird combinations.

To be able to run a test with a specific ABI without constraining it to a
specific triple, new substitutions are added to lit: %itanium_abi_triple and
%ms_abi_triple can be used to get the current target triple adjusted to the
desired ABI. For example, if the test suite is running with the i686-pc-win32
target, %itanium_abi_triple will expand to i686-pc-mingw32.

Differential Revision: http://llvm-reviews.chandlerc.com/D2545

llvm-svn: 199250
</content>
</entry>
<entry>
<title>Prepare for using MS ABI by default for Win32: update CodeGenCXX tests</title>
<updated>2013-12-13T22:43:52+00:00</updated>
<author>
<name>Hans Wennborg</name>
<email>hans@hanshq.net</email>
</author>
<published>2013-12-13T22:43:52+00:00</published>
<link rel='alternate' type='text/html' href='https://git.raptorcs.com/git/bcm5719-llvm/commit/?id=442e4f7f5fc3446b02e97d6b3e11091c8932142e'/>
<id>urn:sha1:442e4f7f5fc3446b02e97d6b3e11091c8932142e</id>
<content type='text'>
llvm-svn: 197281
</content>
</entry>
<entry>
<title>Turn access control on by default in -cc1.</title>
<updated>2010-04-09T19:03:51+00:00</updated>
<author>
<name>John McCall</name>
<email>rjmccall@apple.com</email>
</author>
<published>2010-04-09T19:03:51+00:00</published>
<link rel='alternate' type='text/html' href='https://git.raptorcs.com/git/bcm5719-llvm/commit/?id=3155f573f5ad55a4838d7ea73bfa819ef6be82d3'/>
<id>urn:sha1:3155f573f5ad55a4838d7ea73bfa819ef6be82d3</id>
<content type='text'>
Remove -faccess-control from -cc1; add -fno-access-control.
Make the driver pass -fno-access-control by default.
Update a bunch of tests to be correct under access control.

llvm-svn: 100880
</content>
</entry>
<entry>
<title>Fix for PR6294: we should only delay recording nested dynamic classes if they</title>
<updated>2010-03-07T05:49:51+00:00</updated>
<author>
<name>Eli Friedman</name>
<email>eli.friedman@gmail.com</email>
</author>
<published>2010-03-07T05:49:51+00:00</published>
<link rel='alternate' type='text/html' href='https://git.raptorcs.com/git/bcm5719-llvm/commit/?id=b632e30e41939b9a2253f9ebfa8367c3874402e9'/>
<id>urn:sha1:b632e30e41939b9a2253f9ebfa8367c3874402e9</id>
<content type='text'>
are lexically nested.  Othewise, we never end up recording semantically nested
classes.

llvm-svn: 97900
</content>
</entry>
</feed>
