[llvm-dev] how can i get consumer-typeset exe in debug mode

Ramakota Reddy via llvm-dev llvm-dev at lists.llvm.org
Tue Apr 23 02:03:54 PDT 2019


Thanks Jessica.

With Regards,
Ramakota.

From: jpaquette at apple.com <jpaquette at apple.com>
Sent: Monday, April 22, 2019 9:46 PM
To: Ramakota Reddy <Ramakota.Reddy at arm.com>
Cc: llvm-dev at lists.llvm.org
Subject: Re: [llvm-dev] how can i get consumer-typeset exe in debug mode

Hi Ramakota,

You can get consumer-typeset in debug mode using the -g flag in Clang.

I don’t think this will necessarily help you a lot though. You’re debugging the compiler, not the consumer-typeset source code. Personally, I find the output assembly a bit more useful than actual test source information in this situation.

In situations like this, it’s probably better to see if you can find a SingleSource test failure. These are usually a bit easier to work with than large MultiSource tests. If there are no such failures, you can usually narrow things down by bisecting on object files.

e.g.

1) Compile consumer-typeset with a good compiler
2) Compile consumer-typeset with the compiler you want to debug
3) Link half the object files from the good consumer-typeset with half the object files from the bad consumer-typeset
4) Run the test and see if it fails
5) Repeat until you (hopefully) find one file that causes the issue

From there, you’re usually in a much better position to start debugging the compiler.

- Jessica

On Apr 22, 2019, at 3:15 am, Ramakota Reddy via llvm-dev <llvm-dev at lists.llvm.org<mailto:llvm-dev at lists.llvm.org>> wrote:

Hi All,

I have made some changes in AArch64LoadStoreOptimizer.cpp file and with check-llvm all tests are passing successfully.
But in llvm-test suite some tests are failing, like consumer-typeset tests are failing.

Now I want to debug with ‘consumer-typeset’ exe from SANDBOX. But it is release build.

How can I debug this issue in this case and how can I get ‘consumer-typeset’ exe in debug mode?

Could any one please give your suggestions on this issue.

Thanks & Regards,
Ramakota Reddy.
IMPORTANT NOTICE: The contents of this email and any attachments are confidential and may also be privileged. If you are not the intended recipient, please notify the sender immediately and do not disclose the contents to any other person, use it for any purpose, or store or copy the information in any medium. Thank you. _______________________________________________
LLVM Developers mailing list
llvm-dev at lists.llvm.org<mailto:llvm-dev at lists.llvm.org>
https://lists.llvm.org/cgi-bin/mailman/listinfo/llvm-dev

IMPORTANT NOTICE: The contents of this email and any attachments are confidential and may also be privileged. If you are not the intended recipient, please notify the sender immediately and do not disclose the contents to any other person, use it for any purpose, or store or copy the information in any medium. Thank you.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.llvm.org/pipermail/llvm-dev/attachments/20190423/4622f355/attachment.html>


More information about the llvm-dev mailing list